AT:
- when Optimize is loaded the front-end does only one request against the new ui configuration rest endpoint and stores all this information
- the ui configuration is then retrieved from the central storage whenever needed in the front-end, e.g. for:
- sharing enabled
- email enabled in alerting
- webapps endpoint
- optimize version for footer and the docs link
- the header customization
- the branch
OPT-2623is deleted from the repo - storage is not persisted across page reloads (no local- or session-storage involved)
Context:
Right now, the front-end does a request for each ui configuration parameter against the back-end although this information is static and does not change (except for a migartion or restart of Optimize). Thus, we should store all this information once when the page is loaded and the retrieve it locally instead of doing the same requests over and over again.