Skip to content
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

Closed
3 tasks
betodealmeida opened this issue Feb 2, 2021 · 4 comments
Closed
3 tasks

Consolidate SQL components #12899

betodealmeida opened this issue Feb 2, 2021 · 4 comments
Labels
!deprecated-label:bug Deprecated label - Use #bug instead sqllab Namespace | Anything related to the SQL Lab

Comments

@betodealmeida
Copy link
Member

betodealmeida commented Feb 2, 2021

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

  • 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

@betodealmeida betodealmeida added the #bug Bug report label Feb 2, 2021
@junlincc junlincc added the sqllab Namespace | Anything related to the SQL Lab label Feb 2, 2021
@zuzana-vej zuzana-vej added !deprecated-label:bug Deprecated label - Use #bug instead and removed #bug Bug report labels Apr 20, 2021
@junlincc
Copy link
Member

@betodealmeida can we prioritize it in Q4/Q1 for stability?

@stale
Copy link

stale bot commented Apr 17, 2022

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 .pinned to prevent stale bot from closing the issue.

@stale stale bot added the inactive Inactive for >= 30 days label Apr 17, 2022
@rusackas
Copy link
Member

rusackas commented Feb 2, 2023

@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

  1. Convert it to a SIP and gather support (probably not needed, it doesn't seem controversial)
  2. Convert it to an Ideas thread, and see if folks are interested/supportive.
  3. Simply close it as stale, and revisit the topic when there's time/energy.

@stale stale bot removed the inactive Inactive for >= 30 days label Feb 2, 2023
@rusackas
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
!deprecated-label:bug Deprecated label - Use #bug instead sqllab Namespace | Anything related to the SQL Lab
Projects
None yet
Development

No branches or pull requests

4 participants