JSONAPI-Resources / JSONAPI-Resources/jsonapi-resources
JSON API document parsing maybe could be extracted to its own gem?
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 2.3k
- Forks
- 546
- PR merge metrics
- No merged PRs in 30d
Description
It seems there is a lot of re-doing of parsing a full JSON API document going around.
It would be cool to have a common interface between all the gems that need to work with json api documents.
I was looking at the Request object, and thought that would be a good one to abstract out to its own gem. maybe give it a lightweight interface for accessing the id and the attributes, maybe relationships and their ids and attributes.
thoughts?
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
Begin with the Request object mentioned in the issue and compare how full JSON API documents are parsed across the affected gems. Define the shared interface and extraction boundary, then confirm the proposed gem can expose ids, attributes, relationships, and relationship ids or attributes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100