viaResource & viaResourceId (& viaRelationship) not passed when creating model through the createRelationButton on belongsTo field (modal form)

[BnitoBzh]

• Laravel Version: 8.36.2
• Nova Version: 3.22.0 / 3.23.1
• PHP Version: 7.4.16
• Database Driver & Version: sqlite / pgsql
• Operating System and Version: MacOS
• Browser type and version: Firefox 87.0

Description:

When using BelongsTo Field you can show a "+ Create" button to create a new related model concerned by the field (showCreateRelationButton()method)
This button opens a modal with the form, but the HTTP request that request the form do not pass the viaResource & viaResourceId (& viaRelationship) values.

Detailed steps to reproduce the issue on a fresh Nova installation:

Create two Models

• the First with a BelongsTo relationship to the second
• The Second with (or not) a relationship to the First model (HasOne or HasMany)
• Creates the related nova Resources and Fields
• Use the showCreateRelationButton option on the BelongsTo field on the First model
• Try to create a new First model, and from the creation form, click on the "+ Create" on the right of the select dropdown
• On the browser console, The request to get the Second model form do not pass the viaResource & viaResourceId (& viaRelationship) values.

[crynobone]

Yes that's the expected behaviour right now. What would use case to have it pass to the modal create (second) as viaResourceId isn't available yet at the time.

[BnitoBzh]

The use case is to get the viaResource & viaResourceId values to filter some values in the form.
For example, in the Second model form (in the modal window) it can use some other fields like another BelongsTo i can use these values to filter the BelongsTo model propositions in the related select dropbox (usage of relatableQuery)

[BnitoBzh]

The real fake use case.
I want to create a Post model (that belongsto a Author model, that belongsto a Role model itself), but its Author doesn't exists yet, so i create it by using the showCreateRelationButtonoption. In the Author form, i would like to filter the Role (BelongsTo) field, because if it is an author it cannot be a subcriber (role type). If i get the viaResource, viaResourceId, viaRelationship values i can filter Roles in the relatableRoles function on the Author resource.

I don't know if it's crystal clear ...

[crynobone]

If i get the viaResource, viaResourceId

In that context the viaResource would be Post and viaResourceId isn't available since Post is yet to be created. The Post model has no awareness about role.

[BnitoBzh]

In that context the viaResource would be Post and viaResourceId isn't available since Post is yet to be created. The Post model has no awareness about role.

Ok, here, the viaResourceId is empty, but not required in this example, the viaResource is good enough. The viaResourceId value should not be empty when editing the Post resource, if try to create another User model.

Actually, the viaResource, viaResourceId and viaRelationship values are provided on a HasMany field why it would be different with the BelongsTo field ?

[davidhemphill]

👋 Hi there! In order to keep this repository focused on bug reports, we auto-close feature requests and requests for help. Feel free to post your feature requests so others can discuss and add reactions. We'll keep an eye on them for later planning.

[BnitoBzh]

Feel free to post your feature requests so others can discuss and add reactions

Where ?

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.