Having received great answers to my questions about json_api endpoints, I have just come across a situation where I am requesting “included” resources using the Swagger / OpenAPI UI, which will respond with the public attributes or any “default_fields” set in the related resource’s json_api block. B…

This sounds like a bug. Please work up a reproduction or failing test and submit an issue :slight_smile:

Will do. What are the guidelines and best practices for doing that on this project (and I assume that this is scoped to AshJsonApi)? Also I was stepping through the code yesterday (using pry) to see what is taking place and am happy to continue digging into this further to get a sense of what need…

Ideally a test in a relevant test file, there is a test somewhere for inclusion of related resources IIRC. Barring that, a separate repo with a minimal reproduction. As for this issue, it sounds like there is some kind of mishandling of fields somewhere, like we’re passing it down when rendering re…

I found where the problem lies (for this case). The situation is that I am including a related resource (in this case “Product”) in the GET and relying on the public of default_fields set for that resource. If I set the default_fields for the main “base” resource (in my case “Survey”) in the base_…

Ah, right you are. This is a simple fix, which is that we should only be using the default fields from the route for the top level resource, not for included resources.

great sleuthing! Thank you for finding this :bowing_man:

Elixir Programming Language Forum

AshJsonApi - includes & default_fields

Questions & Help Questions

zachdaniel December 4, 2024, 3:50pm 7

great sleuthing! Thank you for finding this