Skip to content

Extension detected by customization flag #3067

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

Conversation

cenedhryn
Copy link
Contributor

No description provided.

@cenedhryn cenedhryn requested a review from a team as a code owner March 1, 2022 22:09
@cenedhryn cenedhryn requested a review from Bennett-Lynch March 1, 2022 22:09

@Test
public void bucketExists() {
assertThat(s3.doesBucketExist(BUCKET)).isTrue();
Copy link
Contributor

Choose a reason for hiding this comment

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

v1 users rejoice!

It would be nice to test error conditions here as well. E.g., bucket exists but not owned by you.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This is primitive for sure!

@@ -159,5 +159,6 @@
"createMethodParams": [
"clientConfiguration"
]
}
},
"extensionInterface": "software.amazon.awssdk.services.s3.extensions.S3ClientExtensionMethods"
Copy link
Contributor

Choose a reason for hiding this comment

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

When we eventually support async extensions as well, do you foresee having 2 fields here? Would it maybe be simpler to just have the package prefix, and we can infer the rest? Or even a simple boolean if we can infer all of it.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I think a name is better, at least a package name; leads to less inference. When I added this, I had in mind that we just slap Async on, but that's quite ugly. We could either infer both names or add a more complex structure.

@cenedhryn cenedhryn merged commit a71c177 into hackathon-2022-extension-methods Mar 1, 2022
@cenedhryn cenedhryn deleted the salande/hack22-change-extension-location branch March 1, 2022 22:33
@sonarqubecloud
Copy link

sonarqubecloud bot commented Mar 1, 2022

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 2 Code Smells

100.0% 100.0% Coverage
0.0% 0.0% Duplication

aws-sdk-java-automation added a commit that referenced this pull request Jun 13, 2024
…3659d5812

Pull request: release <- staging/39255d97-8c49-4ab7-a750-1473659d5812
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.

2 participants