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

refactor(js_semantic): handle bindings with bogus names #654

Merged
merged 1 commit into from
Nov 2, 2023

Conversation

Conaclos
Copy link
Member

@Conaclos Conaclos commented Nov 2, 2023

Summary

The semantic model assumes that every identifier binding has an associated semantic binding.
This assumption is broken in one case: when the binding has a bogus name.
This PR improves code robustness by handling bindings with a bogus name.
This could fix #650.

Test Plan

I didn't figure out how to create a binding with a bogus name.

@Conaclos Conaclos temporarily deployed to Website deployment November 2, 2023 14:18 — with GitHub Actions Inactive
@github-actions github-actions bot added the L-JavaScript Language: JavaScript and super languages label Nov 2, 2023
Copy link
Contributor

github-actions bot commented Nov 2, 2023

Parser conformance results on

js/262

Test result main count This PR count Difference
Total 49701 49701 0
Passed 48721 48721 0
Failed 980 980 0
Panics 0 0 0
Coverage 98.03% 98.03% 0.00%

jsx/babel

Test result main count This PR count Difference
Total 40 40 0
Passed 37 37 0
Failed 3 3 0
Panics 0 0 0
Coverage 92.50% 92.50% 0.00%

symbols/microsoft

Test result main count This PR count Difference
Total 6322 6322 0
Passed 2036 2036 0
Failed 4286 4286 0
Panics 0 0 0
Coverage 32.20% 32.20% 0.00%

ts/babel

Test result main count This PR count Difference
Total 662 662 0
Passed 592 592 0
Failed 70 70 0
Panics 0 0 0
Coverage 89.43% 89.43% 0.00%

ts/microsoft

Test result main count This PR count Difference
Total 17646 17646 0
Passed 13454 13454 0
Failed 4190 4190 0
Panics 2 2 0
Coverage 76.24% 76.24% 0.00%

@Conaclos Conaclos requested a review from ematipico November 2, 2023 14:39
false
};
let scope_id = self.current_scope_mut().scope_id;
self.stash.push_back(SemanticEvent::DeclarationFound {
scope_id,
hoisted_scope_id,
name_token,
range: node.syntax().text_range(),
Copy link
Member

Choose a reason for hiding this comment

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

Is this intentional? Should it be text_trimmed_range?

Copy link
Member Author

Choose a reason for hiding this comment

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

It is intentional. We use text_range everywhere.
I still plan to change it to text_trimmed_range.

@Conaclos Conaclos merged commit ad364f1 into main Nov 2, 2023
@Conaclos Conaclos deleted the conaclos/js-semantic/improve-code-robustness branch November 2, 2023 15:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
L-JavaScript Language: JavaScript and super languages
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Client Biome: connection to server is erroring. Shutting down server
2 participants