villebro commented on issue #28047: URL: https://github.com/apache/superset/issues/28047#issuecomment-2113614570
Update from design meeting today (@michael-s-molina @rusackas @kasiazjc @justinpark @villebro present): @kasiazjc shared first mocks: Proposal 1 (user/global tabs on top):  Proposal 2 (nav on left hand side):   Quick summary of discussion: - Regular users would only see the user preferences - Admins should be able to edit global defaults through this UI rather than having to make the changes in `superset_config.py`. These would be shown in a separate section with same options as user preferences. - As we're expecting lots of preferences to be added over time, we should introduce a global search that makes it possible to quickly find the relevant preferences - For the UI, it would be preferable to create a new React component that can be used to design the new version of the Explore Control Panel. This way we could introduce global search in the Control Panel, too. - The schema for preferences should probably be stored in a big blob, either in the key-value store or the user object, and support the following features: - versioning: make it possible to migrate to new versions with ease, similar to how the chart migration tool works - be able to mark deprecated preferences - support deep nesting. This will be especially important on the Explore Control Panel, where complex schemas will make it possible to fully leverage the ECharts schema for high customizability of charts The work can roughly be split up in the following major tasks: - Design: next steps to see if we can add deep nesting to the design @kasiazjc - Component design: See if a JSON schema can be created that makes it possible to render the preference section/control panel. @rusackas @michael-s-molina @justinpark - Backend design: User preference blob schema, migration + persistence in backend. @villebro Ping @anamitraadhikari who may be interested in also contributing to the FE work. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
