-
Notifications
You must be signed in to change notification settings - Fork 892
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
[discover] Query editor UI clean up #7896
Conversation
❌ Empty Changelog SectionThe Changelog section in your PR description is empty. Please add a valid changelog entry or entries. If you did add a changelog entry, check to make sure that it was not accidentally included inside the comment block in the Changelog section. |
src/plugins/data/public/query/query_string/language_service/default_language_reference.tsx
Outdated
Show resolved
Hide resolved
src/plugins/data/public/query/query_string/language_service/get_query_control_links.tsx
Outdated
Show resolved
Hide resolved
src/plugins/query_enhancements/public/query_editor/query_language_reference.tsx
Outdated
Show resolved
Hide resolved
const defaultEditor = createEditor( | ||
SingleLineInput, | ||
SingleLineInput, | ||
[createDefaultLanguageReference()], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i see from my earlier comment.
This is already a lot cleaner so def want this in but I think we can think bigger similar to @joshuali925 stuff with the query header extension being a container this could be the same. And I think the naming will help because i was a little confused before.
We could make this more generic. Will comment in my overall thread.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks a lot cleaner. Thank you so much.
I think we can make it more generic. This is more like query editor actions that developers can register
to. Or we can just have a container of queryEditorActions which then lets developers pass any or none in.
But this goes to ensuring the editor is exposed correctly to be reused with the correct state.
Not blocking but i think post 2.17 we should revisit and making it more generic that the editors are exposed and registered completely in the language.
can you make sure the changelog section is accurate |
0838136
b6c055e
to
6f8f08f
Compare
6f8f08f
to
425335f
Compare
Signed-off-by: abbyhu2000 <abigailhu2000@gmail.com>
425335f
to
bcdcd4f
Compare
The backport to
To backport manually, run these commands in your terminal: # Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/OpenSearch-Dashboards/backport-2.x 2.x
# Navigate to the new working tree
pushd ../.worktrees/OpenSearch-Dashboards/backport-2.x
# Create a new branch
git switch --create backport/backport-7896-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 fd8af76ae1327f96f7b7058f24296900bd5817b0
# Push it to GitHub
git push --set-upstream origin backport/backport-7896-to-2.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/OpenSearch-Dashboards/backport-2.x Then, create a pull request where the |
* follow up Signed-off-by: abbyhu2000 <abigailhu2000@gmail.com> * address comments Signed-off-by: abbyhu2000 <abigailhu2000@gmail.com> * Changeset file for PR opensearch-project#7896 created/updated --------- Signed-off-by: abbyhu2000 <abigailhu2000@gmail.com> Co-authored-by: opensearch-changeset-bot[bot] <154024398+opensearch-changeset-bot[bot]@users.noreply.github.com>
* follow up * address comments * Changeset file for PR #7896 created/updated --------- Signed-off-by: abbyhu2000 <abigailhu2000@gmail.com> Co-authored-by: opensearch-changeset-bot[bot] <154024398+opensearch-changeset-bot[bot]@users.noreply.github.com>
Description
Issues Resolved
Screenshot
Testing the changes
Changelog
Check List
yarn test:jest
yarn test:jest_integration