-
-
Notifications
You must be signed in to change notification settings - Fork 9.5k
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
Angular: Use ɵReflectionCapabilities to find component & module metadata #17156
Conversation
☁️ Nx Cloud ReportCI ran the following commands for commit 7d8f3ee. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this branch ✅ Successfully ran 1 targetSent with 💌 from NxCloud. |
the use of '@angular/elements' is no longer necessary for the doc Inline
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.
Hi @ThibaudAV -- it looks like this change breaks a few of the snapshot tests in CI. Can you please take a look?
1af9353
to
7d8f3ee
Compare
@shilman done, Very good test 💌 I hadn't thought about this case |
Angular: Use ɵReflectionCapabilities to find component & module metadata
Issue: #11613 #14828
Surly several with angular 13 or 12 where the recovery of input / output was important. for exemple
And when the ngOnChanges didn't work.
Link to my comment here : #11613 (comment)
link here too : #14828 (comment)
What I did
As Reflect is no longer used by Angular, it is no longer necessary for storybook to rely on it.
I change storybook to use the
ɵReflectionCapabilities
function of Angular which will allow to have the same behavior as an Angular application to find component MetadataHow to test