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

[BUG] Rule crash while typing in-editor due to class shorthand not containing a value. #157

Closed
threehams opened this issue Aug 25, 2022 · 0 comments · Fixed by #158
Closed

[BUG] Rule crash while typing in-editor due to class shorthand not containing a value. #157

threehams opened this issue Aug 25, 2022 · 0 comments · Fixed by #158
Labels
bug Something isn't working

Comments

@threehams
Copy link
Contributor

Describe the bug
A class or className shorthand prop crashes 7 different rules in the project, causing an error to pop up in-editor:

ESLint: Cannot read properties of null (reading 'type') Occurred while linting

To Reproduce
Steps to reproduce the behavior:

  1. Enable the enforces-shorthand rule.
  2. Type: <div class></div>.

Expected behavior
No error

Environment (please complete the following information):

  • OS: macOS
  • Softwares + version used:
    • VSCode 1.70.2
    • npm 8.5.5, node v16.14.2

Additional context
Easily reproducible with tests, PR incoming
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Prevent rule crash from class/className shorthand while typing. threehams/eslint-plugin-tailwindcss
1 participant
@threehams