-
-
Notifications
You must be signed in to change notification settings - Fork 85
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
Bug: Standalone CVA component #3778
Comments
Hi @kekel87, thanks for the report. You need to keep The thing is that |
fix(core): providers with useExisting will be kept if their value is a kept declaration #3778
v14.2.4 has been released and contains a fix for the issue. Feel free to reopen the issue or to submit a new one if you meet any problems. |
Thank you very much for your reactivity. Have a good week. |
You too! Stay in touch! |
@satanTime We are using version |
Hi @LukasMachetanz, could create a min example of the issue? Feel free to submit a new bug. |
Description of the bug
Hi 🙃, I was migrating most of my dumb components to Standalone.
But the tests of the ones implementing
ControlValueAccessor
won't start.I've got this error:
I also tried with NgModel without success (see in example).
Thanks !
An example of the bug
Link: https://stackblitz.com/edit/github-gdvfn5?file=src%2Ftest.spec.ts
Expected vs actual behavior
That the CVA standelone component can be tested with ng-mocks.
The text was updated successfully, but these errors were encountered: