Lorenzo Natali

There are no functional changes in this PR. The refactor involves the geoserver integrations. So please test them on DEV and QA. I tested on myself the integration is working....

Yes, actually dev, qa and stable are running on docker, and they all have data-directory configured. I updated the checkboxes so we can unblock this task.

Excluding: - Backup / versioning of the data dir (that can be delegated to dev ops) - "Remove references for gs-stable to catalog" that needs to be investigated (and the...

I splitted the issue parts to clarify what parts can be postpopned. You can create another issue, or if the investigation gets well keep it in this one.

Just one thing about "mute" stream. Epics of redux-observable already define a 3rd argument, as an arbitrary object to pass (typically to pass APIs that can be wrapped for testing,...

@tdipisa this is not included by default as a panel in default print. Is a separate plug-in, available but not included in the build. Should we include? I don't know...

Sorry for the late feedback. The general idea is good and it doesn't look to generate any problem, looking at the code, at least. Actually I didn't used too much...

Good. only a test for your functionality is sufficient. It is a proof that it retrieves the capabilities and the part you need at the same time.

Hi @landryb, To speed up test development I suggest `npm run continuoustest`. This allows you to re-execute tests on every file save. You can reduce the number of tests executed...

Hi: I fixed the test. The only issue with the test was that you was doing `expect({}).toBe({})` that is like an `===`. You had to use `toEqual` instead, for deep...