Repository navigation
fix(host): report an unreadable argument on any stacked host decorator - #611
Merged
Merged
Conversation
Every stacked `@HostListener` / `@HostBinding` is compiled now, so the lone-surrogate check looks at every one too. A bad argument on a later decorator is reported instead of compiling a fallback (the member name, no listener, no args). Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Member
Author
|
@codex review |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Codex Review: Didn't find any major issues. Another round soon, please! Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #601. That PR compiles every stacked
@HostListener/@HostBindingon a member, butlone_surrogate_host_errorstill checked only the first one. A lone surrogate ('\uD800') in a later decorator got past the check, and a fallback was compiled silently:@HostBinding('title') @HostBinding('\uD800') vɵɵdomProperty("title", ctx.v)("v", ctx.v), a binding named after the member@HostBinding's argument must be a string …@HostListener('click') @HostListener('\uD800') a()@HostListener's event name argument must be a string …@HostListener('click') @HostListener('x', ['\uD800']) a(x)"x"listener with its args droppedFailed to resolve @HostListener.args at position 0 …The check now goes over every matching decorator, the same set the extractors compile. A lone surrogate on the first or only decorator was already reported this way.
Found by Codex on #601 (thread).
Tests
tests/stacked_host_decorators_test.rs: one new test with the three cases above. It fails without the change.cargo test -p oxc_angular_compiler --all-features: 3496 passed.pnpm compare --fixtures: 1162 fixtures, 0 mismatches.pnpm test: 376 passed.🤖 Generated with Claude Code