Add the possibility to use the relation names on the allowedFields. #917
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem:
Package currently converts relation names to plural snake_case in fields parameters, causing inconsistencies when using singular relation names in API requests.
Suppose that I have the bellow model:
I would like to request the userOwnerTestName relationship, my first try was do this:
api/v1/tasks?include=userOwnerTestName&fields[userOwnerTestName]=id,email&fields[tasks]=user_id
and the response is:
But I was expecting:
If I change the request to:
api/v1/tasks?include=userOwnerTestName&fields[user_owner_test_names]=id,email&fields[tasks]=user_id
it works like a charm! But I need to convert the relationship name to plural and use the snake_case format.
Solution:
Introduce a configuration option to control relation name conversion:
Example Usage: