* after authentification, query the categories if active and store them
* get categories from store
* use category store to get categories
* get categories from store
* mock store to have access to categories
* to get rid of the active categories config variable in the frontend, the Category query returns an empty array when categories are not active
* remove CATEGORIES_ACTIVE from .env
* should return string to avoid warnings in console
* replace all env calls for categories active by getter from store
* use categoriesActive getter
* ignore order of returned categories
* mixin to get the category infos from the store, to ensure, that the quey has been called
* fix misspelling
---------
Co-authored-by: Wolfgang Huß <wolle.huss@pjannto.com>
@mattwr18 @alina-beck there seems to be no switch or configuration to
let vue-test-utils or jest fail whenever there is a call to
`console.error`. The only way to test it for very specific tests is
this. I took it from here:
https://geedew.com/catching-prop-validation-in-vue-with-Jest/