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.

Sign up for GitHub

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

Jump to bottom

Inputs should accept undefined/null for compatibility with async #424

Closed

arshaw opened this issue Dec 7, 2022 · 1 comment

Labels

Member

arshaw commented Dec 7, 2022

Created from this comment by @efcoyote:

After selecting the correct target branch you can take a look. The binding of events is still a bit tricky. The async pipe will return EventSourceInput | null or EventSourceInput | undefined | null but the @input expect just EventSourceInput | undefined. The null type is missing.

arshaw added the Confirmed label

arshaw mentioned this issue

Expose events as @Input() again (like in v4) #303

Closed

Member Author

arshaw commented Dec 7, 2022

fixed in v6.0.0-beta.4

arshaw closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment