We have some pieces of immutable config that gets passed from the “outside” into the app, and which currently ends up in the store. This can lead to confusion since, unlike other store data, it’s not meant to be mutable (so should you still get it from the store in a reactive fashion, e.g. using computed(), or is it okay to just get it once in setup?). We would like to clear this up by moving the config out of the store, probably into a separate plugin where components can access it.