Don't check if iterable is nullable, what matters is null-aware calls #4330
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.
Fixes avoid_function_literals_in_foreach_calls fails to handle legacy types #4328.
Reverts Don't report
avoid_function_literals_in_foreach_calls
with null-aware call #4039 that caused false negatives in non-null-safe mode.And reverts skip nullable iterables in
avoid_function_literals_in_foreach_calls
#2752 along with it because it was not the exact right fix in the first place.Null-aware calls are since handled by Don't report avoid_function_literals_in_foreach_calls with null-aware chain #4305 and all the existing tests still pass.