betodealmeida opened a new issue #12899: URL: https://github.com/apache/superset/issues/12899
We currently have a few places where users can write SQL: - SQL Editor - When editing a virtual dataset - When defining a custom metric - (Any other places?) Each one uses a different component for the user to type SQL. Ideally, we should use a single component, making the experience consistent and having features available everywhere (for example, autocompleting function names is only available in SQL Editor). ### Expected results Consistent UX and UI. ### Actual results - NO autocomplete when editing a virtual dataset's query - No autocomplete for *function names* when defining a custom metric via SQL #### Screenshots N/A #### How to reproduce the bug N/A ### Environment (please complete the following information): - superset version: master - python version: N/A - node.js version: N/A ### Checklist Make sure to follow these steps before submitting your issue - thank you! - [ ] I have checked the superset logs for python stacktraces and included it here as text if there are any. - [ ] I have reproduced the issue with at least the latest released version of superset. - [ ] I have checked the issue tracker for the same issue and I haven't found one similar. ### Additional context N/A ---------------------------------------------------------------- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
