-
Notifications
You must be signed in to change notification settings - Fork 78
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
Please remove the null type from IAbstractControl statusChanges observable #550
Comments
Looking at the repository, it seems you already changed the type, but the released version (the one from you get from As a workaround until you release the newest Angular 13 compatible version, I`ll just delete that null from the dist file. |
@ciurte-freelance Will be released today. |
@ajayojha It still wasn`t released |
@ciurte-freelance package has been released. please update the same. |
Describe the bug
Now that Angular 13 came, we got the Angular native
FormControlStatus = 'VALID' | 'INVALID' | 'PENDING' | 'DISABLED'
;This doesn
t fit with the IAbstractControl interface
statusChangesobservable which provides 'VALID' | 'INVALID' | 'PENDING' | 'DISABLED' | null
.Because the RxWeb
s type is larger than the native type, the usual
new FormControl(<ControlProp>{...})` now gives a compilation error.Expected Behavior
In Angular 12 and before you were able to do
new FormControl(<ControlProp<T>>{...})
.To Reproduce
Create an angular 13 project, instal RxWeb types and write
new FormControl(<ControlProp<someType>>{})
and you will get a compilation error that there is a type mismatchPackage Version
@rxweb/types@^1.0.7
The text was updated successfully, but these errors were encountered: