CAConfig Editor: Local Storage Caching prevents displaying new parameters correctly

Description

steps to reproduce:

install our sample application https://github.com/wcm-io/wcm-io-caconfig/tree/develop/sample-app
open a configuration http://localhost:4502/content/contextaware-config-sample/en/config.html#/io.wcm.caconfig.sample.config.ConfigSample
keep the browser open
add a new configuration option to https://github.com/wcm-io/wcm-io-caconfig/blob/develop/sample-app/bundles/core/src/main/java/io/wcm/caconfig/sample/config/ConfigSample.java
deploy the sample application again
refresh the browser window
the new parameter is displayed, but without an entry field, see

workaround - the new parameter is displayed correctly if either:

the browser is closed completely and opened again
browser cache (including local storage) is cleared

Attachments

Linked issues

relates to

WCON-64

Multiple editor reloads on a collection configuration breaks the editor

Activity

Show:

Stefan Seifert June 28, 2020 at 7:52 AM

thanks!

David Ding June 27, 2020 at 12:40 PM

- Fix pushed to project's develop branch.

Stefan Seifert April 28, 2020 at 3:54 PM

yes, i can still reproduce the problem as described, tested on windows with current chrome and firefox
i've not disabled any of the default caching behavior in the browsers

David Ding April 8, 2020 at 10:59 AM

- could you check if this is still reproducible?

I understand why the bug should occur, but when I follow your steps to reproduce, it is working correctly for me (have tried Chrome and Firefox)

Jurgen Brouwer February 21, 2020 at 9:05 AM

Ran into the same issue a couple of times already. The workaround for clearing the local storage works, but it’s easy to miss/forget this step.

This happens often in projects where we have multiple branches that add/remove properties in a config. After a new deployment this would cause the unwanted behaviour.