Fix some upcoming NullAway wildcard warnings by msridhar · Pull Request #5602 · junit-team/junit-framework (original) (raw)

We're starting to work on wildcard support in NullAway (see uber/NullAway#1520), and some warnings turned up when running that NullAway version on JUnit. This PR fixes the warnings. I think the fix makes sense: since ConfigurationParameters#get takes a Function<? super String, ? extends @Nullable T>, org.junit.jupiter.engine.config.JupiterConfiguration#getRawConfigurationParameter should take the same type for its Function parameter.

I hereby agree to the terms of the JUnit Contributor License Agreement.

Definition of Done

Most points N/A as this only changes annotations; no code behavior changes

• There are no TODOs left in the code
• Method preconditions are checked and documented in the method's Javadoc
• Coding conventions (e.g. for logging) have been followed
• Change is covered by automated tests including corner cases, errors, and exception handling
• Public API has Javadoc and @API annotations
• Change is documented in the User Guide and Release Notes