suddjian commented on issue #8655: [SIP-30] Remove Tabs in SQL Lab
URL: 
https://github.com/apache/incubator-superset/issues/8655#issuecomment-588366950
 
 
   @michellethomas 
   
   The redesign of sqllab is being treated as an ever-evolving north star to 
align everyone on while developing Superset. This SIP is just about how we can 
go about achieving a tabless UI.
   
   I agree that feedback from users will be highly useful in implementing the 
new designs, but I think that's out of scope for this SIP. There are other 
ongoing efforts to set up user feedback channels.
   
   Migration is an important part of this work, since this has such a large 
impact on users. My proposal as outlined in the SIP is to give users a button 
to switch to a tabless UI. Until the tabless UI is deemed "stable", there will 
be an option to switch back to tabs, with your tab state kept intact. Before 
you decide to go tabless, we can have a message describing the change to the 
user. We will need to explain that saving queries is the best way to avoid lost 
work, but you will also be able to use the sqllab history feature or your 
browser history to find past queries.
   
   @robdiciuccio 
   
   I think you're correct regarding state management. The way I'm thinking of 
this change is to use the existing tab ID in the same way that you're 
describing a unique session ID. I think migrating to UUIDs or something similar 
is a good idea. We can differentiate between ID types with different URL paths, 
perhaps `/sqllab/saved/:id` and `/sqllab/session/:id`.

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to