Skip to content

fix: Catch more parse errors #97

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
Mar 22, 2025
Merged

fix: Catch more parse errors #97

merged 3 commits into from
Mar 22, 2025

Conversation

nzakas
Copy link
Member

@nzakas nzakas commented Mar 20, 2025

Prerequisites checklist

What is the purpose of this pull request?

Catches some additional parsing errors

What changes did you make? (Give an overview)

  • Added specific error messages for unclosed braces, square brackets, and parentheses (only in strict mode, hidden in tolerant mode)
  • Updated tests
  • Upgraded @eslint/css-tree

Related Issues

Is there anything you'd like reviewers to focus on?

@eslint-github-bot eslint-github-bot bot added the bug Something isn't working label Mar 20, 2025
@github-project-automation github-project-automation bot moved this to Needs Triage in Triage Mar 20, 2025
Copy link
Member

@mdjermanovic mdjermanovic left a comment

Choose a reason for hiding this comment

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

LGTM, thanks!

@mdjermanovic mdjermanovic merged commit d08df74 into main Mar 22, 2025
22 checks passed
@mdjermanovic mdjermanovic deleted the parse-errors branch March 22, 2025 16:43
@github-project-automation github-project-automation bot moved this from Needs Triage to Complete in Triage Mar 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: Complete
Development

Successfully merging this pull request may close these issues.

2 participants