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.

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

Fixed a bug that could cause regexp to issue an error #165

Merged
merged 2 commits into from
Oct 31, 2024

Conversation

Ulyanov-programmer
Copy link
Contributor

I changed the regular expression so that it ignores those places where there are inconvenient characters.

// `a { /*i*/ } /*i2*/ a b {} /*i3*/ a s {}`
// )
// })

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I added this test to see what happens if there are several rules with comments in the description.

The test does not work - it does not connect selectors for the second nested one.
I tried to fix it, but in your code, the devil will break my leg.

Does it make sense to fix it?

@ai ai merged commit 12fc98c into postcss:main Oct 31, 2024
4 checks passed
@ai
Copy link
Member

ai commented Oct 31, 2024

I will release it a few hours later

@ai
Copy link
Member

ai commented Oct 31, 2024

Thanks!

@Ulyanov-programmer
Copy link
Contributor Author

Ulyanov-programmer commented Oct 31, 2024

Oh, but I just fixed the error mentioned above with new commits. You noticed her, didn't you?

The error was that the rules with several nested rules to which comments were attached were incorrectly processed.
Are you sure it's worth releasing?

@ai
Copy link
Member

ai commented Oct 31, 2024

The fix was released in 7.0.1.

Thanks to @Ulyanov-programmer

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