-
Notifications
You must be signed in to change notification settings - Fork 403
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: allow selector utils usage within state class #2210
fix: allow selector utils usage within state class #2210
Conversation
☁️ Nx Cloud ReportCI is running/has finished running commands for commit 81793e5. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this CI Pipeline Execution ✅ Successfully ran 4 targetsSent with 💌 from NxCloud. |
BundleMonFiles updated (2)
Unchanged files (4)
Total files change +1.35KB +1.08% Groups updated (2)
Final result: ❌ View report in BundleMon website ➡️ |
BundleMon (NGXS Plugins)Unchanged files (9)
No change in files bundle size Unchanged groups (1)
Final result: ✅ View report in BundleMon website ➡️ |
BundleMon (Integration Projects)Files updated (1)
Unchanged files (2)
Total files change +17B +0.01% Final result: ✅ View report in BundleMon website ➡️ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, just see my comment
Co-authored-by: Artur <[email protected]>
Code Climate has analyzed commit 81793e5 and detected 0 issues on this pull request. The test coverage on the diff in this pull request is 92.0% (50% is the threshold). This pull request will bring the total coverage in the repository to 95.4% (0.0% change). View more on Code Climate. |
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
The
createPropertySelectors
utility checks that the provided selector is a valid selector.This is great, but if the utility is used within a state class it fails this check (during
ngDevMode
) because the@State
decorator has not yet added the selector metadata.A similar issue exists if a
@Selector
decorated selector is used within the same state class.Issue Number: #2209
What is the new behavior?
These usages are allowed. This was achieved by delaying the "valid selector" check in the dev mode.
Does this PR introduce a breaking change?
Other information