Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Parse many consecutive - as a comment #2240

Merged
merged 1 commit into from
Jul 11, 2023
Merged

Parse many consecutive - as a comment #2240

merged 1 commit into from
Jul 11, 2023

Conversation

janmasrovira
Copy link
Collaborator

@janmasrovira janmasrovira added this to the 0.4.2 milestone Jun 30, 2023
@janmasrovira janmasrovira self-assigned this Jun 30, 2023
@janmasrovira janmasrovira marked this pull request as ready for review June 30, 2023 20:00
@jonaprieto jonaprieto self-requested a review July 11, 2023 08:11
@jonaprieto jonaprieto force-pushed the require-space-after-judoc-start branch from 85b1554 to cee53cc Compare July 11, 2023 08:55
@jonaprieto jonaprieto force-pushed the require-space-after-judoc-start branch from cee53cc to 325ca02 Compare July 11, 2023 09:03
@jonaprieto jonaprieto merged commit 366afb5 into main Jul 11, 2023
@jonaprieto jonaprieto deleted the require-space-after-judoc-start branch July 11, 2023 09:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@jonaprieto jonaprieto jonaprieto approved these changes

Assignees

@janmasrovira janmasrovira

Labels
fix:bug parsing
Projects
None yet
Milestone
0.4.2
Development

Successfully merging this pull request may close these issues.

Comment before the import section leads to the parse error
2 participants
@janmasrovira @jonaprieto