-
Notifications
You must be signed in to change notification settings - Fork 253
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(storage): copy and move APIs #4569
Merged
Jordan-Nelson
merged 4 commits into
feat/storage-gen-2
from
chore/gen-2-storage/copy-move
Mar 21, 2024
Merged
Changes from 2 commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
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 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 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 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 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 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 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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -363,12 +363,12 @@ class AmplifyStorageS3Dart extends StoragePluginInterface | |
|
||
@override | ||
S3CopyOperation copy({ | ||
required StorageItemWithAccessLevel<StorageItem> source, | ||
required StorageItemWithAccessLevel<StorageItem> destination, | ||
required StoragePath source, | ||
required StoragePath destination, | ||
StorageCopyOptions? options, | ||
}) { | ||
final s3Source = S3ItemWithAccessLevel.from(source); | ||
final s3Destination = S3ItemWithAccessLevel.from(destination); | ||
// final s3Source = S3ItemWithAccessLevel.from(source); | ||
// final s3Destination = S3ItemWithAccessLevel.from(destination); | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Are we leaving this in the code to save it for later? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. No. I removed these. |
||
|
||
final s3PluginOptions = reifyPluginOptions( | ||
pluginOptions: options?.pluginOptions, | ||
|
@@ -381,45 +381,13 @@ class AmplifyStorageS3Dart extends StoragePluginInterface | |
|
||
return S3CopyOperation( | ||
request: StorageCopyRequest( | ||
source: s3Source, | ||
destination: s3Destination, | ||
source: source, | ||
destination: destination, | ||
options: options, | ||
), | ||
result: storageS3Service.copy( | ||
source: s3Source, | ||
destination: s3Destination, | ||
options: s3Options, | ||
), | ||
); | ||
} | ||
|
||
@override | ||
S3MoveOperation move({ | ||
required StorageItemWithAccessLevel<StorageItem> source, | ||
required StorageItemWithAccessLevel<StorageItem> destination, | ||
StorageMoveOptions? options, | ||
}) { | ||
final s3PluginOptions = reifyPluginOptions( | ||
pluginOptions: options?.pluginOptions, | ||
defaultPluginOptions: const S3MovePluginOptions(), | ||
); | ||
|
||
final s3Options = StorageMoveOptions( | ||
pluginOptions: s3PluginOptions, | ||
); | ||
|
||
final s3Source = S3ItemWithAccessLevel.from(source); | ||
final s3Destination = S3ItemWithAccessLevel.from(destination); | ||
|
||
return S3MoveOperation( | ||
request: StorageMoveRequest( | ||
source: s3Source, | ||
destination: s3Destination, | ||
options: options, | ||
), | ||
result: storageS3Service.move( | ||
source: s3Source, | ||
destination: s3Destination, | ||
source: source, | ||
destination: destination, | ||
options: s3Options, | ||
), | ||
); | ||
|
Oops, something went wrong.
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.
Why is this test being removed?
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.
I think I removed this because it depended on a test I was removing and it seemed redundant to other e2e tests we have. I added it back though and updated it to no longer be dependent on the other test. We can decide if it is indeed redundant when we refactor the full test suite.