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

docs: update @uppy/aws-s3 docs #5093

Merged
merged 1 commit into from May 16, 2024
Merged

docs: update @uppy/aws-s3 docs #5093

merged 1 commit into from May 16, 2024

Conversation

aduh95
Copy link
Member

@aduh95 aduh95 commented Apr 16, 2024

Refs: #5076
Refs: #5075
Refs: #5070

@aduh95 aduh95 added the 4.0 For the 4.0 major version label Apr 16, 2024
@aduh95 aduh95 requested a review from Murderlon April 16, 2024 15:36
Copy link
Contributor

Diff output files
No diff

Copy link
Member

@Murderlon Murderlon left a comment

Choose a reason for hiding this comment

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

It's the wrong way around, aws-s3-multipart docs should move into aws-s3 and aws-s3-multipart should be removed?

@@ -41,7 +41,7 @@ milliseconds on uploading.

**In short**

- We recommend to set [`shouldUseMultipart`][] to enable multipart uploads only
- We recommend the default value of [`shouldUseMultipart`][], which enable multipart uploads only
for large files.
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
for large files.
for large files (100 MiB).

@aduh95 aduh95 merged commit 89bfe23 into 4.x May 16, 2024
15 of 20 checks passed
@aduh95 aduh95 deleted the aws-plugin-docs-bc branch May 16, 2024 07:09
@Murderlon
Copy link
Member

It's the wrong way around, aws-s3-multipart docs should move into aws-s3 and aws-s3-multipart should be removed?

What about this?

@aduh95
Copy link
Member Author

aduh95 commented May 16, 2024

I don't know if it's worth breaking the existing links. In any case, that can always happen in a follow-up PR, but hopefully we can agree this PR is better merged than not

@Murderlon
Copy link
Member

I won't break links on the website, we can ensure that. If people have GitHub files bookmarked I don't care about breaking those.

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

Successfully merging this pull request may close these issues.

None yet

2 participants