Skip to content

fix: Highlighter isSetup # 556 #579

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

Merged
merged 1 commit into from
Apr 1, 2025

Conversation

GoulielmosFloros
Copy link
Contributor

Description

Added isSetup equals to false for the async function when you dispose the highlighter. Therefore if whenever you specify highlighter.dispose() every time you switch pages the isSetup becomes false.

Reviewed-by: Goulielmos Floros
Ref: #556

Additional context


What is the purpose of this pull request?

  • Bug fix
  • New Feature
  • Documentation update
  • Other

Before submitting the PR, please make sure you do the following:

  • Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
  • Follow the Conventional Commits v1.0.0 standard for PR naming (e.g. feat(examples): add hello-world example).
  • Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
  • Ideally, include relevant tests that fail without this PR but pass with it.

Added isSetup equals to false for the async function when you dispose the highlighter. Therefore if whenever you specify highlighter.dispose() every time you switch pages the isSetup becomes false.

Reviewed-by: Goulielmos Floros
Ref: ThatOpen#556
@HoyosJuan HoyosJuan merged commit 6780230 into ThatOpen:main Apr 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants