Improve federation support

[christophfriedrich]

Make federation info actually available to the utilised vue-components Collection, Collections, Processes, FileFormats.

[m-mohr]

Thanks. Setting to draft until we have a new version number for the JS client so that we can also update the dependency in the package.json.

The same request as in the Vue components: A screenshot would be nice ;-)

[christophfriedrich]

Good point that the dependency needs to be released and filled in before it makes sense to merge this.

---

Screenshot of FederationMissingNotice in Collections:

In Processes and FileFormats it looks alike. If nothing is missing, the notice just isn't there at all.

I didn't implement the ⚠️ icons yet that you wished for in #230 (comment), just concentrated on getting the Notices to work for now.

---

Screenshot of FederationNotice in Collection if it's online:

Currently still accompanied by FederationMissingNotice if it's offline:

That is redundant, which I addressed in Open-EO/openeo-vue-components#100, but I was kinda waiting for your feedback on Open-EO/openeo-vue-components#101 before changing it.

[m-mohr]

Thanks. We can keep it as is for now, the ⚠️ is more a nice-to-have, I'd say.

I've added more details to the issues and the PRs in vue-components.

[christophfriedrich]

Screenshots:

Example in modal:

Example in wizard:

Example in user content panel:

[m-mohr]

Suggested change

	...Utils.mapState(namespace, ['missing']),
	...Utils.mapState(namespace, {data: namespace}),
	...Utils.mapState(namespace, ['pages', 'hasMore']),
	...Utils.mapState(namespace, {data: namespace}),
	...Utils.mapState(namespace, ['missing', 'pages', 'hasMore']),

[christophfriedrich]

I kinda liked keeping all federation stuff together (line 28 and 29) and separating it from the rest (first two lines federation, then the rest)

[m-mohr]

I'd like to keep it as concise as possible to avoid potential confusion, I also had to look for a second to realize it's the same namespace. We also kept it together in all other instances.

[christophfriedrich]

Fair enough, sounds reasonable too

[m-mohr]

The missing is not initiated in the getDefaultState method above, I could imagine that this could become an issue and lead to the reactivity issues you faced

[christophfriedrich]

Good spot!! I added it to getDefaultState and the weird behaviour indeed went away. Let's see if this fix is more permanent now 😆

[christophfriedrich]

While taking the screenshots I realised that sometimes the FederationMissingNotice is displayed in the orangered colour it's supposed to have, sometimes in the darkgoldenrod of the FederationNotice:

I was able to reproduce: It is orange as long as no FederationNotice has been added to the DOM, then it changes to gold.

Probably need to adapt CSS specificity in FederationMissingNotice to overwrite more permanently, or not use the same class names for the two components in the first place. Could also make the style scoped? <style lang="scss" scoped>...