microsoft / microsoft/process-migrator
Migrator does not migrate layout items in the same order
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 113
- Forks
- 61
- PR merge metrics
- No merged PRs in 30d
Description
The process finished successfully and all the layout items were migrated successfully, the issue is that they were not migrated in the same order.
I had these columns:
[Custom]
Status
Details
I'm expecting that after migration they will be the same, meaning same values and order, but it did not.
After migration it looked like this:
Status
Details
[Custom]
The solution for this issue should be that after migration items should look like the source before migration.
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
Start by tracing the layout-item migration flow and compare the source and destination sequences shown in the issue. Confirm how items are read and created, then verify that a migration preserves both 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
- 42/100