Replies: 2 comments
-
I assume you refer to the following part of the spec where it states:
When I quickly looked at our implementation, it seems that fields which are ignored (not defined in sparse field set) also do not get included when requested through
Option 1 is fairly involved. Could you therefore more elaborate on your use case why you need included resources even though you do not know by the request to what resource those are connected? |
Beta Was this translation helpful? Give feedback.
-
Hello @sliverc , Actually, it was something wrong with my implementation, By calling this: I get the correct data. thank u |
Beta Was this translation helpful? Give feedback.
-
Hello, thank u so much for the help.
Does the package have this feature; using sparse fields and include at the same time.
From the below url, i am trying to filter the "name" field from the "device" resource, and at the same time "include" the related resource; "lots"
From json:api documentation, this feature is present, but not sure if it is present in the django json api package.
From json:api documentaiton :
Here is the response that i get:
The field filtering is correct, but the include related resource is not present.
Thank u so much
Beta Was this translation helpful? Give feedback.
All reactions