A lot of the logic we have for dealing with different user types and permissions involves checking user attributes and switching what gets displayed inside vue components.
In certain situations, it might be cleaner to handle this at the action/vuex layer to keep components more single-purpose. Potentially something to think about when migrating to vuex2.
A lot of the logic we have for dealing with different user types and permissions involves checking user attributes and switching what gets displayed inside vue components.
In certain situations, it might be cleaner to handle this at the action/vuex layer to keep components more single-purpose. Potentially something to think about when migrating to vuex2.
cc @jonboiser @rtibbles
migrated from https://trello.com/c/zTyFEtMb/800-design-implement-route-or-action-based-handling-of-various-user-types