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
Currently, when a row is clicked in the index form, the logic to instantiate the detail form and open it in the sidesheet happens in the index form.
Should we perhaps separate those concerns?
e.g. We hold the 'currently selected item somwhere as part of the global state and make it reactive. The index form tabulator would then simply update that current selection.
We'd then have a render effect somewhere to control what happens as a result of that change - in the demo, that would open the sidesheet with the selected item displayed within the correct detail form.
The text was updated successfully, but these errors were encountered:
We could route to a module instead of a form and do all the url handling there - something similar to an MVC controller. That could then handle the opening of the index and detail forms.
Currently, when a row is clicked in the index form, the logic to instantiate the detail form and open it in the sidesheet happens in the index form.
Should we perhaps separate those concerns?
e.g. We hold the 'currently selected item somwhere as part of the global state and make it reactive. The index form tabulator would then simply update that current selection.
We'd then have a render effect somewhere to control what happens as a result of that change - in the demo, that would open the sidesheet with the selected item displayed within the correct detail form.
The text was updated successfully, but these errors were encountered: