kasiazjc commented on PR #34642:
URL: https://github.com/apache/superset/pull/34642#issuecomment-3206386876

   > one idea, not sure if it's good, would be to make `validate` primary and 
`save` secondary when "unvalidated", and flip `save` to become primary once 
it's validated (?)
   > 
   > Moving the validate above seems to break the validate linear flow though 
(generally top-down) doesn't it?
   
   I think changing  button hierarchy can be confusing, so if would suggest 
approach of - disable save if sql not validated to make sure that it works. 
What do you think? 


-- 
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: notifications-unsubscr...@superset.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org
For additional commands, e-mail: notifications-h...@superset.apache.org

Reply via email to