-
Notifications
You must be signed in to change notification settings - Fork 19
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
bugfix: S3C-2899 support v1 in Delimiter, DelimiterMaster #1028
bugfix: S3C-2899 support v1 in Delimiter, DelimiterMaster #1028
Conversation
Hello jonathan-gramain,My role is to assist you with the merge of this Status report is not available. |
Integration data createdI have created the integration data for the additional destination branches.
The following branches will NOT be impacted:
Follow integration pull requests if you would like to be notified of |
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
Peer approvals must include a mandatory approval from @jonathan-gramain. |
lib/algos/list/delimiterMaster.js
Outdated
skipping() { | ||
if (this.vFormat === BucketVersioningKeyFormat.v0) { |
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.
Just want to mention the idea of having each version be either a class or an object instead of putting a bunch of these if's around. Could have just one if in a factory method somewhere then everything else is standard.
Mabye a base Bucket Version class if there is a lot of similarities.
Alternatively, an object that maps the v0 and v1 methods around in one place.
Something along the lines of:
const versionRouter = {
[BucketVersioningKeyFormat.v0]: {
skipping: this.skippingV0,
other: this.otherv0,
},
[BucketVersioningKeyFormat.v1]: { etc }
}
// then map through this:
versionRouter[this.vFormat].skipping()
// make wrap it with a check the version exists if required
Anyway, just ideas.
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.
It sounds better indeed since there is a common pattern, especially after the migration states are introduced (v0 to v1)
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.
updated
tests/unit/algos/list/tools.js
Outdated
}, | ||
}, | ||
]; | ||
testCases.forEach(testCase => { |
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 am pretty sure you can reduce some typing here by doing this:
testCases.forEach(({v0Params, v1Params}) => {
// can then just use v0Params instead of testCase.v0Params
}
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.
Ah yeah, did not think about using object deconstruction here
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.
updated
24faf5e
to
a3e73fe
Compare
History mismatchMerge commit #24faf5e6ba5698a10bf0037b71ca8e6ec93fe2d1 on the integration branch It is likely due to a rebase of the branch Please use the |
a3e73fe
to
334c2bf
Compare
@bert-e reset |
Reset completeI have successfully deleted this pull request's integration branches. |
Integration data createdI have created the integration data for the additional destination branches.
The following branches will NOT be impacted:
Follow integration pull requests if you would like to be notified of |
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
Peer approvals must include a mandatory approval from @jonathan-gramain. |
The two listing methods Delimiter and DelimiterMaster now support v1 versioning key format in addition to v0. Modify the listing algo classes to support buckets in v1 versioning key format, in addition to v0. Enhance existing unit tests to check the result of getMDParams()
334c2bf
to
fb89b4e
Compare
History mismatchMerge commit #b431e35857eb1715ad5038b817bad58dd18c94cf on the integration branch It is likely due to a rebase of the branch Please use the |
@bert-e reset |
Reset completeI have successfully deleted this pull request's integration branches. |
Integration data createdI have created the integration data for the additional destination branches.
The following branches will NOT be impacted:
Follow integration pull requests if you would like to be notified of |
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
Peer approvals must include a mandatory approval from @jonathan-gramain. |
Branches have divergedThis pull request's source branch To avoid any integration risks, please re-synchronize them using one of the
Note: If you choose to rebase, you may have to ask me to rebuild |
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
Peer approvals must include a mandatory approval from @jonathan-gramain. |
@bert-e approve |
In the queueThe changeset has received all authorizations and has been added to the The changeset will be merged in:
The following branches will NOT be impacted:
There is no action required on your side. You will be notified here once IMPORTANT Please do not attempt to modify this pull request.
If you need this pull request to be removed from the queue, please contact a The following options are set: approve |
I have successfully merged the changeset of this pull request
The following branches have NOT changed:
Please check the status of the associated issue S3C-2899. Goodbye jonathan-gramain. |
The two listing methods Delimiter and DelimiterMaster now support v1
versioning key format in addition to v0.
Modify the listing algo classes to support buckets in v1 versioning
key format, in addition to v0.
Enhance existing unit tests to check the result of getMDParams()
Requires merging PR #1018 first.