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.

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

feat(iot-dev): Fix file upload complete notification API #911

Merged
merged 1 commit into from Sep 11, 2020

Conversation

timtay-microsoft
Copy link
Member

@timtay-microsoft timtay-microsoft commented Sep 9, 2020

completeFileUploadAsync does not behave asynchronously, so the name was a mistake. Deprecating that API and creating a new one without the Async suffix

#910

completeFileUploadAsync does not behave asynchronously, so the name was a mistake. Deprecating that API and creating a new one without the Async suffix
@timtay-microsoft
Copy link
Member Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 4 pipeline(s).

Copy link
Member

@abhipsaMisra abhipsaMisra left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this required for the .NET client as well?

@vinagesh
Copy link
Member

Looks good. Should we patch the LTS ?

@timtay-microsoft
Copy link
Member Author

Is this required for the .NET client as well?

No, because it is actually async in .NET

This java function returns syncrhonously, so it should never have been post-fixed with "async"

@timtay-microsoft
Copy link
Member Author

Looks good. Should we patch the LTS ?

It isn't really a critical bug fix or a security fix, so I don't see a reason to

@vinagesh
Copy link
Member

Looks good. Should we patch the LTS ?

It isn't really a critical bug fix or a security fix, so I don't see a reason to

When do we finally delete the deprecated functions?

@timtay-microsoft
Copy link
Member Author

Looks good. Should we patch the LTS ?

It isn't really a critical bug fix or a security fix, so I don't see a reason to

When do we finally delete the deprecated functions?

Never, probably

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants