-
Notifications
You must be signed in to change notification settings - Fork 463
feat(storage): add deleteSourceObjects option to Bucket::compose() #9211
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
Open
salilg-eng
wants to merge
8
commits into
googleapis:main
Choose a base branch
from
salilg-eng:feat/delete_source_objects
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+210
−0
Open
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
e460bfe
Implementation delete source object when file merge using compose
salilg-eng d82c34b
Unit Test case
salilg-eng 173d7ab
Sorted Gemini review
salilg-eng a167c71
Updated one
salilg-eng 28b5b1f
Merge branch 'main' into feat/delete_source_objects
salilg-eng 283213b
Merge branch 'main' into feat/delete_source_objects
salilg-eng 48294d0
fix(storage): validate deleteSourceObjects parameter type
salilg-eng 26e992e
Merge branch 'main' into feat/delete_source_objects
salilg-eng File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If the option is a bool we should enforce the bool:
currently If the user passes a
['deleteSourceObjects'] = 52the check for$deleteSourceObjectswould be "true" even if the value is not a boolean.It might behave as expected, but I strongly believe we should let the user know that a parameter is the wrong parameter.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for the excellent feedback! Enforcing strict type checking for
deleteSourceObjectsis a great safety addition to prevent loose 'truthy' evaluations.Regarding the implementation: in PHP, the
instanceofoperator is reserved only for checking objects against class/interface structures and does not support checking primitive types (likebool,string,int). Calling$val instanceof boolon a real boolean will look for a class namedbool, returnfalse, and therefore always throw the exception.To resolve this, I've implemented the validation using PHP's built-in primitive validation function
is_bool():There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh yeah! My bad! haha it is in fact not instanceof bool but
is_bool, you got it!