[java] validate capturePerformance requirements in build() #269
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nadvolod
reviewed
Jul 23, 2021
Contributor
nadvolod
left a comment
nadvolod
left a comment
There was a problem hiding this comment.
@titusfortner love small PRs! The code makes sense.
- Does it make sense to add a test for this case?
- I see that the Checks are failing for Java 8 and 9
- I see that there are a few Codacy complaints. Can you see those and are they valid in your opinion?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This addresses #267
This should be a good pattern going forward of addressing incompatibilities in the overridden build() method.