leanprover / leanprover/lean-workbench
Evaluate moving Prisma stuff into shared/
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 9
- Forks
- 1
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 35
Description
In #125 @Vtec234 noted that I'd created a type User that wasn't exported but needed to be a supertype of the derived Prisma user type, and sensibly points out that this is the problem we'd tried to avoid by creating a shared workspace in the first place. Perhaps Prisma generation belongs 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 tracing the shared workspace, the unexported User type, and the derived Prisma user type. Determine whether Prisma generation belongs in shared/; done means the project has an agreed placement and the type relationship no longer requires the workaround described here.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- database
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100