feat(x2a): add action to resync project migration#3196
Conversation
|
Important This PR includes changes that affect public-facing API. Please ensure you are adding/updating documentation for new features or behavior. Changed Packages
|
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #3196 +/- ##
==========================================
+ Coverage 60.97% 61.03% +0.05%
==========================================
Files 2098 2101 +3
Lines 65140 65310 +170
Branches 17029 17075 +46
==========================================
+ Hits 39721 39863 +142
- Misses 25180 25199 +19
- Partials 239 248 +9
*This pull request uses carry forward flags. Click here to find out more. Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
mareklibra
force-pushed
the
FLPATH-3214.recalculateModuleList
branch
2 times, most recently
from
056afe2 to
a32aae0
Compare
Signed-off-by: Marek Libra <marek.libra@gmail.com>
mareklibra
force-pushed
the
FLPATH-3214.recalculateModuleList
branch
from
a32aae0 to
8767d35
Compare
| technology?: ReturnType<typeof normalizeSourceTechnology>; | ||
| }> = []; | ||
|
|
||
| for (const mm of metadataModules) { |
There was a problem hiding this comment.
This fucntion is almost impossible to follow, should we have an abstraction here? It's 100 lines more of code, and It does so many things, that I think that It should be break to avoid scenarios where this is going to be difficult to debug.
|
2 participants
Fixes: FLPATH-3214
The user can newly update the project migration plan in an external flow and then let the X2A resync the module list changes.
resync.mp4