justinpark opened a new pull request, #45392:
URL: https://github.com/apache/superset/pull/45392

   ### SUMMARY
   
   Adopt the client tool API previously [implemented on the dashboard-v2 
branch](https://github.com/apache/superset/pull/43093), following SIP #43488, 
and implement SQL Lab tools first.
   
   The SQL Lab tools reuse existing frontend APIs to inspect and update editor 
SQL, manage tabs, and trigger query execution. They register under the 
core.sqlLab__* namespace through the shared client tool registry.
   
   Tool | Description
   -- | --
   core.sqlLab__get_current_editor_id | Get the active SQL editor tab ID.
   core.sqlLab__get_editor_tabs | List open tabs with their titles, database 
IDs, catalogs, and schemas.
   core.sqlLab__get_databases | List database IDs and names already loaded in 
SQL Lab.
   core.sqlLab__get_editor_sql | Read the active editor’s SQL, selected text, 
and tab metadata.
   core.sqlLab__update_editor_sql | Replace the active editor’s SQL without 
executing it.
   core.sqlLab__create_editor_tab | Create a tab with a title, database, and 
optional SQL, catalog, and schema.
   core.sqlLab__switch_editor_tab | Activate an existing tab by editor ID.
   core.sqlLab__close_editor_tab | Close an existing tab by editor ID.
   core.sqlLab__run_current_query | Execute the active editor’s selected text, 
or full SQL when nothing is selected, and return the client query ID.
   
   
   Handlers validate inputs and return structured errors for invalid arguments, 
missing tabs, API failures, or calls made outside SQL Lab.
   
   ### BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
   N/A
   
   ### TESTING INSTRUCTIONS
   
   specs
   
   ### ADDITIONAL INFORMATION
   <!--- Check any relevant boxes with "x" -->
   <!--- HINT: Include "Fixes #nnn" if you are fixing an existing issue -->
   - [ ] Has associated issue:
   - [ ] Required feature flags:
   - [ ] Changes UI
   - [ ] Includes DB Migration (follow approval process in 
[SIP-59](https://github.com/apache/superset/issues/13351))
     - [ ] Migration is atomic, supports rollback & is backwards-compatible
     - [ ] Confirm DB migration upgrade and downgrade tested
     - [ ] Runtime estimates and downtime expectations provided
   - [x] Introduces new feature or API
   - [ ] Removes existing feature or API
   


-- 
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]

Reply via email to