You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 21, 2022. It is now read-only.
Currently if the parameter in the constructor is null, it is still assigned to
the related property.
In a patch to collection-setter-injector plugin (issue 13), list properties can
now be instantiated with an empty ArrayList.
Thus, it would be nice if the value-constructor does not replace the default
instantiated empty list with null if the it is passed in the constructor's
parameters.
Environment
Operating System: All
Platform: All
Affected Versions
[current]
The text was updated successfully, but these errors were encountered:
ozgwei said:
This issue itself does not depend on issue 11.
However, the patch I have just attached is built on top of the patch I submitted
for issue 11. So the patch itself depends on issue 11.
Just to clarify the dependency.
kohsuke said:
Looking at the code, it doesn't look like Lexi is the owner of the plugin.
Would you like me to set you up with the commit access so that you can commit
this change? Maybe the original author has moved on, and I don't want your patch
to be in the limbo forever.
If the author does have a problem with your change, we could still roll back
your change later.
Currently if the parameter in the constructor is null, it is still assigned to
the related property.
In a patch to collection-setter-injector plugin (issue 13), list properties can
now be instantiated with an empty ArrayList.
Thus, it would be nice if the value-constructor does not replace the default
instantiated empty list with null if the it is passed in the constructor's
parameters.
Environment
Operating System: All
Platform: All
Affected Versions
[current]
The text was updated successfully, but these errors were encountered: