Clean up code naming of Binary, Engine, Library, Engine Binary, Engine Type, Binary Type etc
Open
Nobody has claimed this yet.
kind/tech
tech/typescript
topic: binary
topic: engine
topic: prisma-client
- Dominant language
- TypeScript
- Stars
- 47.6k
- Forks
- 2.5k
- Avg merge
- 21h 59m
- Merged PRs (30d)
- 95
Description
Right now it is all over the place. We should make sure all uses in variables, classes and functions are consistent with a pattern we decide on.
Contributor guide
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
The issue names no files, tests, or entry points. Start by inventorying the uses of Binary, Engine, Library, Engine Binary, Engine Type, and Binary Type across variables, classes, and functions, then establish the naming pattern before changing references. Done means the selected terminology is consistent throughout the affected code.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend, databases
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100