You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I was using JsonApiFramework 2.1.0, I was able to include not related models to a model without defining any relationship in JsonApiWriter or Mapping. I just simply pass an empty string as its relationship name.
For example, food and vehicle are not related to each other. When I want to include vehicles with food, I just call .IncludeMany(food, String.Empty, vehicles)
However, when I update from 2.1.0 to 2.8.0, it complains about the relationship name. It requires a valid one. However, I don't want to define a fake relationship name because those models are not really related. I just want to get everything in one API call. I believe we cannot use it that way since the 2.2.0 update
Could you please tell me if we have any way to do that?
Thank you very much.
The text was updated successfully, but these errors were encountered:
@tylerton I am trying to understand your issue and if it is still an issue. You want to include unrelated resource(s) in the included section of a json:api document? Can you provide an example JSON document on what you are asking for? Also it seems this would violate the specification when it talks about full linkage?
Hello team,
When I was using JsonApiFramework 2.1.0, I was able to include not related models to a model without defining any relationship in JsonApiWriter or Mapping. I just simply pass an empty string as its relationship name.
For example, food and vehicle are not related to each other. When I want to include vehicles with food, I just call
.IncludeMany(food, String.Empty, vehicles)
However, when I update from 2.1.0 to 2.8.0, it complains about the relationship name. It requires a valid one. However, I don't want to define a fake relationship name because those models are not really related. I just want to get everything in one API call. I believe we cannot use it that way since the 2.2.0 update
Could you please tell me if we have any way to do that?
Thank you very much.
The text was updated successfully, but these errors were encountered: