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
The information which perspectives are available for a user and which perspective is the currently active one is stored in the user table for the perspectives in the classic bundle (perspectives and activePerspective columns).
We need to find a way to integrate the logic for the new perspectives too. Please keep in mind that it is needed to somehow make it possible that studio UI and classic bundle work in parallel. I'd say it's ok when setting the perspectives permissions is only possible in the related UI (so for classic bundle in classic bundle and for studio in studio). Not sure if extending the user entity in the core for studio is a good idea or if it would be better to create a new additional table within studio? With this approach we could keep the core clean from studio related things (and at some point after sunsetting the classic bundle we could deprecate the properties in the core...).
The text was updated successfully, but these errors were encountered:
The information which perspectives are available for a user and which perspective is the currently active one is stored in the user table for the perspectives in the classic bundle (
perspectives
andactivePerspective
columns).We need to find a way to integrate the logic for the new perspectives too. Please keep in mind that it is needed to somehow make it possible that studio UI and classic bundle work in parallel. I'd say it's ok when setting the perspectives permissions is only possible in the related UI (so for classic bundle in classic bundle and for studio in studio). Not sure if extending the user entity in the core for studio is a good idea or if it would be better to create a new additional table within studio? With this approach we could keep the core clean from studio related things (and at some point after sunsetting the classic bundle we could deprecate the properties in the core...).
The text was updated successfully, but these errors were encountered: