-
-
Notifications
You must be signed in to change notification settings - Fork 56
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
possible bug using formBuilder #32
Comments
In the examples that are available in the readme they cast the controls to FormControl that is provided by the lib.
I am not sure if it is intended like this, but it does work: https://stackblitz.com/edit/angular-ivy-tpmydz |
interesting, I'll certainly give that a shot, thanks! If that does work, possibly should add it to the formBuilder section of the docs. Not sure where you saw that but I went back to see if I missed it in there and it isn't covered there |
Yes, this is the current behavior. See issue 23. You're welcome to add this to the form builder section. |
I'm submitting a...
Current behavior
controls created using formBuilder do not appear to have all the features that they should
In this sample shown, using a directly created form control by copy pasting from the docs, the
errors$
observable is present. However, trying to access theerrors$
on my control created using formBuilder gives me a TS linting error saying it doesn't exist and suggesting the vanilla errors objectExpected behavior
As far as I can tell from the docs, it sounds like controls made with formBuilder should also be fully featured. I checked other items like
disabled$
etc and none of them appear on the item made with formBuilderMinimal reproduction of the problem with instructions
just create something with formBuilder and try to access items like
errors$
What is the motivation / use case for changing the behavior?
To fix what appears to be broken behaviour (I apologize if I am just doing something wrong here or misinterpreting how it should work, in which case possibly a clarification added to the docs could help instead?)
Environment
The text was updated successfully, but these errors were encountered: