René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"[v11] Sparse fieldsets allow for invalid types","articleBody":"## This issue is a (choose one):\r\n\r\n- [x] Problem/bug report.\r\n- [ ] Feature request.\r\n- [ ] Request for support. **Note: Please try to avoid submitting issues for support requests. Use [Gitter](https://gitter.im/cerebris/jsonapi-resources) instead.** \r\n\r\n## Checklist before submitting:\r\n\r\n- [x] I've searched for an existing issue.\r\n- [ ] I've asked my question on [Gitter](https://gitter.im/cerebris/jsonapi-resources) and have not received a satisfactory answer.\r\n- [ ] I've included a complete [bug report template](https://github.com/cerebris/jsonapi-resources/blob/master/lib/bug_report_templates/rails_5_master.rb). This step helps us and allows us to see the bug without trying to reproduce the problem from your description. It helps you because you will frequently detect if it's a problem specific to your project.\r\n- [ ] The feature I'm asking for is compliant with the [JSON:API](http://jsonapi.org/) spec.\r\n\r\n## Description\r\n\r\nWhen specifying sparse fieldsets, if you specify the type as the singular version of the type (i.e. `fields[user]=name` instead of `fields[users]=name`, the request succeeds instead of returning a 400.\r\n\r\n### Bug reports:\r\n\r\nOn the `v0-11-dev` branch with Ruby 3.3.5. The root of the issue is that `classify` is used to look up the resource class, which works the same for `user` and `users`, they both become `UserResource`, but then `parse_fields` doesn't verify that the type matches after getting the resource class back. ","author":{"url":"https://github.com/adamkiczula","@type":"Person","name":"adamkiczula"},"datePublished":"2024-11-15T00:28:25.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/1460/jsonapi-resources/issues/1460"}