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
This was originally added to the "to consider" column by @craig-rueda. It sounds like the work required to do this is just deleting /superset from the route names everywhere. Is there more to it than that?
The text was updated successfully, but these errors were encountered:
this seems like a huge task, lot of endpoint on the /superset api are still in use. Is the idea that we will break existing chart/dashboard/explore links or will setting up redirects to the new urls be in scope?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. For admin, please label this issue .pinned to prevent stale bot from closing the issue.
Closing this as stale, but it seems obsolete anyway since it was created for a project board. If this has work we want to consider for 3.0, we should add a new proposal to that board instead. Thanks all!
See SIP-74.
This was originally added to the "to consider" column by @craig-rueda. It sounds like the work required to do this is just deleting
/superset
from the route names everywhere. Is there more to it than that?The text was updated successfully, but these errors were encountered: