Description
While testing the Query Editor, I encountered three related UX issues. None are release-blocking, but they would be useful improvements for a follow-up patch.
1. Run the permission check before opening the Query Editor
The permission prompt appears only after attempting to create a query, once the Query Editor webview has already opened. At that point, the prompt lacks context for the user.
Consider performing a preflight permission check before showing the webview so the permission prompt appears as part of the action that opens the Query Editor.
2. Explain why Run is disabled
When the user does not have permission to run queries, the Run button is disabled without any visible explanation. Details are written to the output channel, but that is difficult to discover.
Show the reason close to the disabled control, for example in its tooltip or as an inline message, and provide a discoverable path to more details.
3. Prevent the AI (Preview) label from wrapping
The AI (Preview) toolbar label wraps onto two lines even when the toolbar has sufficient horizontal space. Keep the label on one line.
Expected behavior
- Permission requirements are checked before the Query Editor webview is displayed, where feasible.
- A user can discover why Run is disabled without searching the output channel.
- The AI (Preview) toolbar label does not wrap.
Description
While testing the Query Editor, I encountered three related UX issues. None are release-blocking, but they would be useful improvements for a follow-up patch.
1. Run the permission check before opening the Query Editor
The permission prompt appears only after attempting to create a query, once the Query Editor webview has already opened. At that point, the prompt lacks context for the user.
Consider performing a preflight permission check before showing the webview so the permission prompt appears as part of the action that opens the Query Editor.
2. Explain why Run is disabled
When the user does not have permission to run queries, the Run button is disabled without any visible explanation. Details are written to the output channel, but that is difficult to discover.
Show the reason close to the disabled control, for example in its tooltip or as an inline message, and provide a discoverable path to more details.
3. Prevent the AI (Preview) label from wrapping
The AI (Preview) toolbar label wraps onto two lines even when the toolbar has sufficient horizontal space. Keep the label on one line.
Expected behavior