[backend] Split playbook components into separated files (#14283)#14728
[backend] Split playbook components into separated files (#14283)#14728MTorbay-Filigran merged 13 commits intomasterfrom
Conversation
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## master #14728 +/- ##
==========================================
- Coverage 32.38% 32.37% -0.01%
==========================================
Files 3098 3107 +9
Lines 211071 213278 +2207
Branches 38242 38420 +178
==========================================
+ Hits 68345 69044 +699
- Misses 142726 144234 +1508
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
| } | ||
|
|
||
| export const PLAYBOOK_MANIPULATE_KNOWLEDGE_COMPONENT: PlaybookComponent<ManipulateConfiguration> = { | ||
| id: 'PLAYBOOK_MANIPULATE_KNOWLEDGE_COMPONENT', |
There was a problem hiding this comment.
This component id has been renamed from PLAYBOOK_UPDATE_KNOWLEDGE_COMPONENT to PLAYBOOK_MANIPULATE_KNOWLEDGE_COMPONENT. We can't rename component ids, otherwise all previously created playbooks with this component will fail, and we would need to migrate them.
SouadHadjiat
left a comment
There was a problem hiding this comment.
keep the component ids the same as before the refactoring
Proposed changes
Related issues
Checklist
Further comments