-
Notifications
You must be signed in to change notification settings - Fork 14.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consolidate SQL components #12899
Comments
@betodealmeida can we prioritize it in Q4/Q1 for stability? |
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 |
@betodealmeida curious your thoughts on how to handle this issue since it's pretty stale, and not a bug, per se. I think the options are
|
Closing this as stale, but maybe we can move forward with this as a SIP when the time comes. There have been other related issues about moving from ACE editor to more modern alternatives, which would likely be a part of this. |
We currently have a few places where users can write SQL:
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
Screenshots
N/A
How to reproduce the bug
N/A
Environment
(please complete the following information):
Checklist
Make sure to follow these steps before submitting your issue - thank you!
Additional context
N/A
The text was updated successfully, but these errors were encountered: