leanprover / leanprover/lean-workbench
/data folder migrations
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 9
- Forks
- 1
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 35
Description
In #125 I'm (probably?) introducing a backwards-compatibility check for projects created before the PR is merged. A better solution would be creating a not-database data migration system, @Vtec234 proposes a plausible design here.
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 reading issue #125 and the proposed design in PR #125's linked comment. Identify how projects created before the PR are currently handled and determine the scope of a non-database migration system for the /data folder. Done means the agreed migration design is implemented and preserves compatibility for older projects.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100