On Tue, Oct 12, 2021 at 10:14 AM Goyot, Martin <[email protected]>
wrote:
> Thanks for your input. I agree with the readResolve but then I'm wondering
> about the maintainability of the class. Let's say in a future version I add
> another field, and in a next one yet another. My readResolve is going to be
> huge and complicated to deal with. Is there some kind of pattern to do it
> right ?
>
In general the pattern is to just not rename fields.
Adding new fields doesn't need readResolve support unless you want a
different value than the default (0, false, null). This is why new options
are often phrased so the legacy default behavior corresponds to the default
field value ("dontDoWhatever" field names are common).
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7Pt%2BzNKUL_wa66GYkrsQ3ja%3D85OdddSODjv29QTjRMmCycw%40mail.gmail.com.
