UserMapperBasedResolver incorrectly parses a boolean using Boolean.getBoolean (which checks system properties) instead of Boolean.parseBoolean.
This is not a blocker as for this code the default value when no parameter is present is true, and when the parameter is present given that the system property has no reason to exist the value will be false; so both values can be covered.
- is caused by
-
NXP-25062 Expose create and update flags through contribution for UserMapperBasedResolver
- Resolved
- Is referenced in