-
Description:I am thinking there is a bug with inline relation creation. I have a resource that has a belongsToMany exactly as shown below.
Which generates this view When I click the + button I was expecting the via resource values to be the parent resource that has the BelongsToMany field to be present in the network request, however they are all empty
I'd expect the via fields to be set based on the
Am I crazy or is this a bug? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
Hi, I don't believe this is a bug. At the point of inline create the relationship is yet to be attached and adding the additional props doesn't 100% useful (since you can create the relationship) and simply cancel attaching. |
Beta Was this translation helpful? Give feedback.
-
The additional props can be useful to determine which fields one might show or which options are loaded in select fields for instance. Maybe you want to show an extra field if the request is made via a specific relationship. |
Beta Was this translation helpful? Give feedback.
Hi, I don't believe this is a bug. At the point of inline create the relationship is yet to be attached and adding the additional props doesn't 100% useful (since you can create the relationship) and simply cancel attaching.