[Auto Suggest] SQL Syntax Highlighting fix

[paulstn]

Description

Fixes SQL monaco monarch tokens by separating the states for single quoted and double quoted strings so that both can appear properly

Previously:

Screen.Recording.2024-11-26.at.4.44.26.PM.mov

Fixed:

Screen.Recording.2024-11-26.at.4.47.28.PM.mov

Issues Resolved

Screenshot

Testing the changes

Changelog

• fix: SQL syntax highlighting double quotes

Check List

• All tests pass
  • yarn test:jest
  • yarn test:jest_integration
• New functionality includes testing.
• New functionality has been documented.
• Update CHANGELOG.md
• Commits are signed per the DCO using --signoff

[github-actions]

❌ Empty Changelog Section

The 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.

[github-actions]

❌ Empty Changelog Section

The 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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 60.88%. Comparing base (073a9ff) to head (94dbd42).
Report is 105 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #8951   +/-   ##
=======================================
  Coverage   60.87%   60.88%           
=======================================
  Files        3802     3802           
  Lines       91072    91072           
  Branches    14375    14375           
=======================================
+ Hits        55444    55446    +2     
+ Misses      32086    32085    -1     
+ Partials     3542     3541    -1     

Flag	Coverage Δ
Linux_1	29.02% <ø> (ø)
Linux_2	56.39% <ø> (ø)
Linux_3	37.90% <ø> (+<0.01%)	⬆️
Linux_4	29.00% <ø> (ø)
Windows_1	29.03% <ø> (ø)
Windows_2	56.34% <ø> (ø)
Windows_3	37.90% <ø> (+<0.01%)	⬆️
Windows_4	29.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[kavilla]

@paulstn does this need to make it to a next branch?

[paulstn]

@kavilla Not too sure what other branches it should be in, but it wasn't made to go into any other branch so probably no.

[opensearch-trigger-bot]

The backport to 2.19 failed:

The process '/usr/bin/git' failed with exit code 128

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.19 2.19
# Navigate to the new working tree
pushd ../.worktrees/OpenSearch-Dashboards/backport-2.19
# Create a new branch
git switch --create backport/backport-8951-to-2.19
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 8f58bceec42038554f84c6f7a5ad6be58f847cfb
# Push it to GitHub
git push --set-upstream origin backport/backport-8951-to-2.19
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/OpenSearch-Dashboards/backport-2.19

Then, create a pull request where the base branch is 2.19 and the compare/head branch is backport/backport-8951-to-2.19.