[ ] Request for support. Note: Please try to avoid submitting issues for support requests. Use Gitter instead.
Checklist before submitting:
[x] I've searched for an existing issue.
[ ] I've asked my question on Gitter and have not received a satisfactory answer.
[ ] I've included a complete bug report template. 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.
[ ] The feature I'm asking for is compliant with the JSON:API spec.
Description
When 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.
Bug reports:
On 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.
This issue is a (choose one):
Checklist before submitting:
Description
When specifying sparse fieldsets, if you specify the type as the singular version of the type (i.e.
fields[user]=nameinstead offields[users]=name, the request succeeds instead of returning a 400.Bug reports:
On the
v0-11-devbranch with Ruby 3.3.5. The root of the issue is thatclassifyis used to look up the resource class, which works the same foruserandusers, they both becomeUserResource, but thenparse_fieldsdoesn't verify that the type matches after getting the resource class back.