-
Notifications
You must be signed in to change notification settings - Fork 642
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
S3: Make eTag naming consistent #2741
Conversation
@@ -89,13 +99,13 @@ object MultipartUploadResult { | |||
location: Uri, | |||
bucket: String, | |||
key: String, | |||
etag: String, | |||
eTag: String, |
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.
AFAIK this can break source compatibility (i.e. if someone calls apply
with named parameters specifically within Scala) but it doesn't break binary compatibility.
@@ -104,13 +114,13 @@ object MultipartUploadResult { | |||
location: akka.http.javadsl.model.Uri, | |||
bucket: String, | |||
key: String, | |||
etag: String, | |||
eTag: String, |
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.
AFAIK this can break source compatibility (i.e. if someone calls create
with named parameters specifically within Scala) but it doesn't break binary compatibility.
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.
Mima on Travis is happy with your changes https://app.travis-ci.com/github/akka/alpakka/jobs/540918111
LGTM.
The intention of this PR is to make
eTag
/ETag
consistent. This was done with internal private API but also the public API whereMultipartUploadResult
usedetag
/getEtag
/getEtag
where as every other public model usedeTag
/getETag
/withETag
. Since this is a public API I addeddeprecated
methods so that people are warned when using the old inconsistent etag naming and to maintain binary compatibility.There is one case where (I think) source compatibility is broken but NOT binary compatibility (see comments). Unfortunately I couldn't get mima running in Alpakka to verify this, I am getting the following error when I run
s3 / mimaReportBinaryIssues