Is there any other options for creating foldable sectionsthat will also work
with the pipeline syntax generator? optionalBlock: will not add the fields
inside the foldableblock to the generated syntaxoptionalProperty: couldn’t get
that to work and I’m notsure that it will indent the child fields like
optionalBlockSimple independent fields: lose visual queue that field
isdependant on another field being set
On Thursday, 19 January 2017 5:13 AM, Jesse Glick <[email protected]>
wrote:
On Tue, Jan 17, 2017 at 7:55 PM, <[email protected]> wrote:
> When updating a plugin to support pipeline script, how do I handle an
> optionalBlock section?
Do not use `f:optionalBlock`. This is a low-level control. Do not
refer to `JSONObject` either. All this is old-style deprecated form
binding.
Use a high-level control like `f:optionalProperty` for nullable
structs (`ui-samples-plugin` has an example), or simple independent
`f:checkbox`es for `boolean` properties (`doCheck*` form validation
can reject invalid combinations).
Also use `@DataBoundSetter` for any property with a plausible default.
--
You received this message because you are subscribed to a topic in the Google
Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/jenkinsci-dev/uGVIkV7u78Y/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
[email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr0KKVKGvJzvgBBAEGdDNshQ%3DY8wgtrzyXsuPst4y60fag%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
--
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/673807624.2364733.1486370659547%40mail.yahoo.com.
For more options, visit https://groups.google.com/d/optout.
