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

[BUG] last-child:mb-0 doesn't raise a warning about being invalid #305

Open
sbdchd opened this issue Jan 13, 2024 · 1 comment
Open

[BUG] last-child:mb-0 doesn't raise a warning about being invalid #305

sbdchd opened this issue Jan 13, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@sbdchd
Copy link

sbdchd commented Jan 13, 2024

Describe the bug

<div className="last-child:mb-0 mb-2" />

Doesn't raise a warning about being invalid, the correct name is last:mb-0

To Reproduce

Use the following css and find no error is raised

<div className="last-child:mb-0 mb-2" />

Expected behavior
Raises error

Screenshots

Environment (please complete the following information):

  • OS: [e.g. macOS, windows 10]
  • Softwares + version used:
    • [e.g. VSCode 1.54.3]
    • [... Terminal 2.9.5, npm 6.14.5, node v14.5.0]

Additional context
Add any other context about the problem here.

eslint config file or live demo
By providing a link to a live demo, a demo video or a github repo fixing the issue will be easier.

@sbdchd sbdchd added the bug Something isn't working label Jan 13, 2024
@kachkaev
Copy link
Contributor

This feature request is reflected in README.md → Upcoming rules as validate-modifiers.

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
None yet
Development

No branches or pull requests

2 participants