jamesplease / jamesplease/api-pls
Determine Resource Model "types"
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 10
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Right now, the types in a Resource Model map directly to SQL types. I mean, they are literally plopped right into a SQL statement, unfiltered. I need to figure out how I want to support these things. It will probably be with some sort of ORM-like system, but I'd rather not have to write that myself if an existing one exists.
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
The issue names no files, tests, or entry points. Start by locating Resource Model type handling and the SQL construction; the issue does not define an ORM choice or a testable definition of done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, postgresql
- Domain
- api, backend, database
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100