microsoft / microsoft/process-migrator
Migrator does not migrate states in the same order
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 113
- Forks
- 61
- PR merge metrics
- No merged PRs in 30d
Description
When the process migration finished, it did migrate all the states correctly but the order is not correct.
If we have the states A, C, B (in the given order), after the migration it will become A, B and C.
Solution:
The states order should be the same (values and order) as the source. AKA: A, C, B
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Trace the migration handling for process states and compare the source state sequence with the generated sequence. Verify the result with an input ordered A, C, B; the work is done when migration preserves both state values and their original order.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs, typescript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100