JSONAPI-Resources / JSONAPI-Resources/jsonapi-resources
UUID route path constraint allows comma-separated ids.
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 2.3k
- Forks
- 546
- PR merge metrics
- No merged PRs in 30d
Description
Why does the constraint allow comma-separated UUIDs? I tried this with the show action, but got a { "title": "Invalid field value", "detail": "02b2dd45-c7a5-4632-8523-2ab3a68411ae,5fe60d71-9f9f-40ff-8f29-266403cb0b6f is not a valid value for id.", ... }.
This feature would be nice, and the spec does not mention URL design except as a recommendation, but even that does not mention CSV for resource id.
JR Version: 0.7.0
Commit: d5675ae446adcd2733b3996d0b5154d4c1de5e2e
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 reproducing the comma-separated UUID request against the show action and trace the UUID route path constraint that handles the id. Check the existing request or constraint tests, if present, and clarify whether comma-separated ids should be accepted or rejected; done means the behavior and resulting validation response match the agreed URL design.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rails, ruby
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100