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

fix(unstable): don't error on non-existing attrs or type attr #27456

Merged
merged 2 commits into from
Dec 27, 2024

Conversation

marvinhagemeister
Copy link
Contributor

When running selectors for JS linting plugins we would error when encountering an unknown attribute name:

// selector
Foo[non-existant]

// error
Error: Missing string id: <number>

This was caused by using 0 as the invalid marker, but also overloading 0 with an actual node type. So the fix is to reserve 0 as the invalid marker and move the property type to the next index.

Copy link
Member

@bartlomieju bartlomieju left a comment

Choose a reason for hiding this comment

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

LGTM

@marvinhagemeister marvinhagemeister merged commit fdd0edf into main Dec 27, 2024
17 checks passed
@marvinhagemeister marvinhagemeister deleted the fix-lint-attr branch December 27, 2024 21:46
dsherret pushed a commit that referenced this pull request Jan 9, 2025
When running selectors for JS linting plugins we would error when
encountering an unknown attribute name:

```js
// selector
Foo[non-existant]

// error
Error: Missing string id: <number>
```

This was caused by using `0` as the invalid marker, but also overloading
`0` with an actual node type. So the fix is to reserve `0` as the
invalid marker and move the property type to the next index.
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