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
I've looked at many of the major user-related plugins (particularly those that provide a user profile edit page + 2fa) and it appears that many of them have landed on a similar architecture:
1 edit page that house multiple sections
Each section of the form (e.g. profile, password, 2fa, browser sessions, etc) is a separate component
The components each have a title, description, form schema/actions, and a sort weight.
The components are either autodiscovered or are manually registered + the only thing the actual edit profile page does is build a form from each of the discovered profile form components, sorted by weight.
This architecture makes a ton of sense and it's interesting that many plugins have independently converged on this structure. I see that 2fa is a built-in feature in 4.x, so that might make sense to turn into one of those form components.
I think that it also makes sense to use the same kind of setup for the tenant edit page: the page itself is a container to which other components can be added.
Since there are so many different attempts at solving this problem in the plugin ecosystem and many of them have arrived at the same conclusion/architecture, does it make sense to build this into Filament itself?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I've looked at many of the major user-related plugins (particularly those that provide a user profile edit page + 2fa) and it appears that many of them have landed on a similar architecture:
This architecture makes a ton of sense and it's interesting that many plugins have independently converged on this structure. I see that 2fa is a built-in feature in 4.x, so that might make sense to turn into one of those form components.
I think that it also makes sense to use the same kind of setup for the tenant edit page: the page itself is a container to which other components can be added.
Since there are so many different attempts at solving this problem in the plugin ecosystem and many of them have arrived at the same conclusion/architecture, does it make sense to build this into Filament itself?
Beta Was this translation helpful? Give feedback.
All reactions