Config Editor: Default values are not displayed

Description

some configurations of the sample application have default values, example

these default values are contained in the JSON response (effectiveValue), but are not displayed in the configuration editor.

example URLs:

Activity

Show:
David Ding
March 22, 2017, 5:08 AM

- Should a default effectiveValue become a "real" value whenever the user saves the config - even if they do not edit the default value?

e.g.
There is a config with

  • stringParam0: default=false; value="user set this before"

  • stringParam1: default=true; effectiveValue="defaultValue1"

If the user modifies stringParam0, does not modify stringParam1 and then clicks Save, what is included in the POST:
stringParam1: null or stringParam1: defaultValue1?

Stefan Seifert
March 22, 2017, 5:47 AM

Should a default effectiveValue become a "real" value whenever the user saves the config - even if they do not edit the default value?

yes, the value should become a "real value".

David Ding
March 22, 2017, 9:24 PM
Stefan Seifert
March 22, 2017, 11:20 PM

thanks!

Fixed

Assignee

Unassigned

Reporter

Stefan Seifert

Labels

None

Components

Affects versions

Priority

Major