-
由 Matt Moore 提交于
By converting several optionalBlock entries to use inline="true", we convert the submitted JSON from: "hasPropertyFoo": { "propertyFoo": "value" }, which is a somewhat unnatural naming scheme, to: "hasPropertyFoo": true, "propertyFoo": "value", This enables us to use the pattern: if(json.optBoolean("hasPropertyFoo", json.has("propertyFoo"))) { ... } To permit either of the following as JSON blobs, for specifying a value for "propertyFoo": 1) "hasPropertyFoo": true, # What comes through from jelly "propertyFoo": "value", 2) "propertyFoo": "value", It also allows any of the following as JSON blobs, for NOT specifying a value for "propertyFoo": 3) "hasPropertyFoo": false, # What comes through from jelly "propertyFoo": "value", 4) "hasPropertyFoo": false, 5) (nothing specified) NOTE: The main interest in flexibility in what JSON comes through is in support of: https://wiki.jenkins-ci.org/display/JENKINS/YAML+Project+Plugin, this is also the purpose of the couple renames that are mixed in with this.
eec43983