fix: lexing of annotations with namespace#12
Open
ShortDevelopment wants to merge 1 commit intoopenqasm:mainfrom
Open
fix: lexing of annotations with namespace#12ShortDevelopment wants to merge 1 commit intoopenqasm:mainfrom
ShortDevelopment wants to merge 1 commit intoopenqasm:mainfrom
Conversation
5 tasks
ShortDevelopment
added a commit
to LEQO-Framework/leqo-backend
that referenced
this pull request
Jun 19, 2025
We're using [`openqasm-pygments`](https://pypi.org/project/openqasm-pygments/) for syntax highlighting `openqasm3` in our docs. As this package contains a bug in lexing indented annotations, we're now using a custom version until the upstream [PR](openqasm/openqasm-pygments#12) is merged.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The old regex had a nested capture-group to match the optional namespace in annotations.
This capture-group was categorized as
Token.Text.Whitespaceand caused incorrect syntax highlighting.We're now using a non-capturing group for the namespace part to not treat the nested group as extra token.
Fixes #11