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

Do not throw an exception if the etag is not set in metadata #44189

Merged

Conversation

artonge
Copy link
Contributor

@artonge artonge commented Mar 14, 2024

Currently, if no etag is set for the metadata, the caller need to wrap getEtag in a try/catch, else, the provider will always fail at the same place. This returns an empty string instead of throwing.

@artonge artonge self-assigned this Mar 14, 2024
@artonge artonge requested a review from ArtificialOwl March 14, 2024 10:16
@artonge artonge added 3. to review Waiting for reviews feature: files php Pull requests that update Php code bug labels Mar 14, 2024
@artonge artonge added this to the Nextcloud 29 milestone Mar 14, 2024
@artonge artonge force-pushed the artonge/fix/do_not_throw_exception_if_etag_is_not_set branch from 3fe77a6 to 8205de7 Compare March 14, 2024 10:19
Copy link
Contributor

@susnux susnux left a comment

Choose a reason for hiding this comment

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

Makes sense and is consistent with out other getETag functions

@Altahrim Altahrim mentioned this pull request Mar 14, 2024
@artonge artonge requested a review from come-nc March 16, 2024 12:38
@skjnldsv skjnldsv merged commit 2954d52 into master Mar 16, 2024
160 checks passed
@skjnldsv skjnldsv deleted the artonge/fix/do_not_throw_exception_if_etag_is_not_set branch March 16, 2024 13:09
@Altahrim Altahrim mentioned this pull request Mar 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3. to review Waiting for reviews bug feature: files php Pull requests that update Php code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants