from developer point of view:
If I retrieve this ${custom.adFrequency} in JSP and define defaultValue as “0.5” in config.json
and forget/skip pb:adFrequency=“0.75” in pb-inc in some other feature
I’d expect ${custom.adFrequency}=“0.5” when page is rendered, and not ${custom.adFrequency}=“"
I should still see ${custom.adFrequency} = "0.75" if I include pb:adFrequency=“0.75” in pb:inc-feature element.
defaultValue in json is kind of misleading, the way it works now is more like initialValue.
we probably don't want to change how embed works now by default; but we can have a flag like useDefaults="true", which will enforce this and make sure default values are used when field is missing.
Categories | Developer Tools, Developer Workflow, New Functionality |
I need it... | Week |
PB include feature no longer exists with PB Engine and we are not making any updates to PB Classic.