Remove migration utility
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 24
- Forks
- 41
- Avg merge
- 3d 13h
- Merged PRs (30d)
- 12
Description
Now that most (all?) adaptors have been moved into the monorepo, should we remove the migration utility?
Keeping it in the codebase incurs a maintenance cost - any time we change standards, conventions, or add tooling, the migration utility will need an update.
Frankly I think it served its purpose and should be gracefully retired to a sunny code silo somewhere.
I suggest we also remove or simplify the migration guide section of the readme.
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 locating the migration utility and the migration guide section in the README, then verify that the adaptors have moved into the monorepo. Done means the obsolete utility is removed or retired cleanly and the README migration guidance is removed or simplified without leaving broken references.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- documentation, tooling
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100