Return null in getBestStatements if there are none #432
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.
StatementGroup requires at least one statement, so calling
getBestStatements if there are no best statements previously would throw
a "non-empty list of statements must be provided" validation error.
Another solution may be to remove the assertation that statement groups cannot be empty.
Then we could return an empty statement group instead of null.
Having no best statement can happen if there is only a deprecrated
statement in the statement group.