Expected Behavior
RegisteredClient.Builder has various @Nullable properties - id, clientId, clientSecret, etc. and can be initialised from an existing RegisteredClient. The fluent setters for these properties should also have @Nullable parameters.
Current Behavior
Passing null to these methods has no ill-effect, but analysis tools flag it as an error.
Context
When constructing a client from input data you want to be able to use the fluent interface, and not add null checks around every method to avoid calling it.
Expected Behavior
RegisteredClient.Builderhas various@Nullableproperties -id,clientId,clientSecret, etc. and can be initialised from an existingRegisteredClient. The fluent setters for these properties should also have@Nullableparameters.Current Behavior
Passing
nullto these methods has no ill-effect, but analysis tools flag it as an error.Context
When constructing a client from input data you want to be able to use the fluent interface, and not add null checks around every method to avoid calling it.