suddjian edited a comment on pull request #17145: URL: https://github.com/apache/superset/pull/17145#issuecomment-946083688
The goal with moving from `POST` to an `<a>` link was to improve UX by allowing proper browser controls (such as "open in a new tab" vs in-tab navigation). It's usually good UX practice to navigate using links. I'd really like to understand better what the differences are between the POST solution and this one, to be able to solve your issues. The `getExploreLongUrl` function is also used by Explore to set the url, so presumably any issues with long urls would also apply there. I think a workable plan to get rid of the long url issue permanently could be to set up some kind of "exploration context" object in the db that has all this information and can be referenced by 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. 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]
