fix(deps): update dependency monaco-editor to v0.31.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
monaco-editor	0.29.1 -> 0.31.0

---

Release Notes

microsoft/monaco-editor

v0.31.0

Compare Source

• adds support for highlighting non basic ASCII, invisible or ambiguous unicode characters.
• adds support for setting an editor banner
• streaming hover results in case of multiple hover providers
• fixes multiple IME issues

Thank you

• @​activeguild (j1ngzoue): Add 'browser-ems-vite-react' sample PR #​2767
• @​emojiiii (C.Y.Kun): Fix some errors on the website playground PR #​2779
• @​gitpaladin (Chen Minglong): Fix token while missing syntax= directive PR #​2809
• @​jonatanklosko (Jonatan Kłosko): Update Elixir tokenization of sigil modifiers PR #​2806
• @​MasterOdin (Matthew Peveler)
  • Update builtin functions for mysql PR #​2749
  • Update list of keywords for redshift PR #​2757
  • Remove return from example addAction PR #​2772
• @​milahu: fix link to monaco.d.ts PR #​2769
• @​Pranomvignesh (Pranom Vignesh): Semantic Tokens Provider Sample is broken in docs PR #​2764
• @​rramo012 (Rafael Ramos): Fixing the documentation links PR #​2748

v0.30.1

Compare Source

• Fixes a performance regression where all languages would be loaded when loading the first language.

v0.30.0

Compare Source

• adds support for rendering horizontal guides between bracket pairs and improves the vertical rendering to account for content in between brackets.
• adds new hover.above option to control the hover position.
• adds ICodeEditor.onDidChangeHiddenAreas which is fired when folding/unfolding.
• to address CVE-2021-42574, the editor now renders Unicode directional formatting characters by default. The special rendering can be turned off using renderControlCharacters. See https://code.visualstudio.com/updates/v1\_62#\_unicode-directional-formatting-characters for an explanation.

Breaking Changes

• renamed enum members of monaco.KeyCode to align with the names given for browser codes.
• renamed ITextModel.getModeId() to ITextModel.getLanguageId()
• renamed IPasteEvent.mode to IPasteEvent.languageId

Thank you

Contributions to monaco-editor-webpack-plugin:

• @​silverwind: Fix letter case in repo URL PR #​165

Contributions to monaco-languages:

• @​arlosi (Arlo Siemsen): Rust: highlighting raw strings and fix chars with escapes PR #​167
• @​MasterOdin (Matthew Peveler)
  • Add new functions in postgresql 14 PR #​168
  • Update json functions for postgresql PR #​169
  • Add missing postgresql functions PR #​170

---

Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, click this checkbox.

---

This PR has been generated by WhiteSource Renovate. View repository job log here.

[pull-request-quantifier-deprecated]

This PR has 10 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : Extra Small
Size       : +5 -5
Percentile : 4%

Total files changed: 2

Change summary by file extension:
.json : +1 -1
.yaml : +4 -4

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer
    iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detetcted.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will
  interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification)
  of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.