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
Short description of what this feature will allow to do:
Right now there seems to be no possibility to modify the TomSelect behaviour trough PHP definitions, one must re-initialize TomSelect selects in a very complex way by injecting custom JS into a CRUD controller, then modifying TomSelect to your needs.
This way, I could specify the form to allow one one selection, regardless of its Assignment. In the frontend, the user then would be able to select only one element.
This is useful when you have a complex relation between elements.
For example in my case, I have a Task, that is a ManyToMany relation to Groups, which is owned by a User (in a OneToMany relation).
So: Many Tasks have Many groups, which individually belong to one User.
In this case, EasyAdmin can only cover the first relation, with no possibility to have the second constraint in mind. By allowing a developer to form the select himself, it will be easier to cover complex relationship scenarios.
The text was updated successfully, but these errors were encountered:
Short description of what this feature will allow to do:
Right now there seems to be no possibility to modify the TomSelect behaviour trough PHP definitions, one must re-initialize TomSelect selects in a very complex way by injecting custom JS into a CRUD controller, then modifying TomSelect to your needs.
This is obviously a bit bad.
Example of how to use this feature
This way, I could specify the form to allow one one selection, regardless of its Assignment. In the frontend, the user then would be able to select only one element.
This is useful when you have a complex relation between elements.
For example in my case, I have a Task, that is a ManyToMany relation to Groups, which is owned by a User (in a OneToMany relation).
So: Many Tasks have Many groups, which individually belong to one User.
In this case, EasyAdmin can only cover the first relation, with no possibility to have the second constraint in mind. By allowing a developer to form the select himself, it will be easier to cover complex relationship scenarios.
The text was updated successfully, but these errors were encountered: