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.
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: introduce
java.time
methods and variables #1671feat: introduce
java.time
methods and variables #1671Changes from 2 commits
3ad5d32
8f4e430
ab5edaa
f66f830
728a6f0
f74d1ee
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Oh I see
DurationDuration
here as well. Hmm, let's see if we can a way to work around this.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 have a couple ideas:
getExecutionDurationJavaTime
getExecutionDurationJT
getExecutionJavaTimeDuration
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.
Responded in googleapis/java-storage#2826 (comment)
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.
Ok, I think either
getExecutionDurationJavaTime
orgetExecutionJavaTimeDuration
should work. JT might be confusing to know that JT referencesjava.time
.I think
getExecutionDurationJavaTime
actually sounds better since it keeps the original method name togethergetExecutionTime
. Let's get Cindy and the Storage SME to agree since I think we should be consistent on the choice.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.
@cindy-peng
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 like
getExecutionJavaTimeDuration
the best since it has the same suffix as other methods. But eithergetExecutionJavaTimeDuration
orgetExecutionDurationJavaTime
sounds good to me. We can follow the same decision for Java-storage.