Skip to content

Fix broken syntax highlighting after the first submodule #339

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 3 commits into from
Sep 29, 2024

Conversation

FedericoPonzi
Copy link
Collaborator

@FedericoPonzi FedericoPonzi commented Sep 29, 2024

Fixes #284
image
image
image

I was also able to verify the update with a test.

@FedericoPonzi FedericoPonzi force-pushed the issue-284 branch 2 times, most recently from 86742a7 to 823392b Compare September 29, 2024 12:04
Copy link
Member

@lemmy lemmy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

a regex is being used to identify a module but there are
actually two regexes, one for the start token and one for
the end (see line 151 and 166). This section define the
patterns that can be found inside the body, by adding
 `#module` I'm allowing recursively searching for modules.

Signed-off-by: Federico Ponzi <[email protected]>
@FedericoPonzi
Copy link
Collaborator Author

I've reworded the commit message, and pushed an additional commit to fix the warning I've forgot to push in the other pr.

Signed-off-by: Federico Ponzi <[email protected]>
@FedericoPonzi FedericoPonzi merged commit 250ef51 into tlaplus:master Sep 29, 2024
4 checks passed
@FedericoPonzi FedericoPonzi deleted the issue-284 branch September 29, 2024 16:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

Broken syntax highlighting after the first submodule
2 participants