vedantprajapati17 commented on issue #33044: URL: https://github.com/apache/superset/issues/33044#issuecomment-2796935723
> May we look at this feature as a begining of dashboards versioning? I do understand that statuses and versions are two quite different things. But hiding functionality seems to be a crossing point here. Do these features actually affect each other? Maybe some minor tweaks can be done now so that further evolution is simplier. how would the dashboards versioning work? would multiple versions of a dashboard be published/draft? archiving sets all current dashboard and previous versions to archived. I think it makes sense to keep an enum for the scope of this SIP. With dashboard versioning we need to define if its all of the dashboard versions we'll be archiving and it will effectively be multiplicative in the number of dashboards created in the DB. -- 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]
