Skip to content
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

None is not supported yet #23

Closed
ankitkumarr opened this issue Oct 22, 2020 · 0 comments · Fixed by #24
Closed

None is not supported yet #23

ankitkumarr opened this issue Oct 22, 2020 · 0 comments · Fixed by #24
Assignees
@ankitkumarr

Comments

@ankitkumarr
Copy link
Contributor

When any binding is unavailable such that the datatype that is received is null, we get a NotSupportedException. We need to also handle the case for TypedData.DataOneofCase.None.

We probably need to handle a bunch of other types as well in future. But None, I think, is more crucial than others.
@ankitkumarr ankitkumarr self-assigned this Oct 22, 2020
@ankitkumarr ankitkumarr mentioned this issue Oct 22, 2020
Merged
@ghost ghost locked as resolved and limited conversation to collaborators Mar 12, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@ankitkumarr ankitkumarr

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix issue when binding data is null Azure/azure-functions-dotnet-worker
1 participant
@ankitkumarr