- Unit and Integration tests now use "inject" instead of starting a server
  and using supertest.
- Add Coverage Reports and "test:dev" mode. This enables a mocha --watch
  like workflow using nodemon, as --watch does not work with esm modules.
- Reorganized and renamed files and functions

michael.kainz authored 2 years ago and julian.baeume committed 2 years ago

This endpoint can be used to dynamically generate pwa.json based on configuration
on the java middleware.

Set cache control to no-store. The ui-middleware will then only look at the remote servers for the files and never in the local cache

this should help to get insights about how the caches are filled locally

Cache lookups will immediately register a promise to prevent multiple requests for the same ressource

Root cause: If multiple connections are opened at the same time after an update, the ui-middleware will do multiple requests to get initial data. That went especially worse, when e2e-tests are launched against ui-middlewares with multiple clients connecting at the same time.
Soltion: Make sure, that a node already caches stuff without a response.

Root cause: configuration was only reloaded on those nodes, that did the version update. The other nodes might not notice that.
Solution: On propagated version changes, the nodes always check for config changes

Root cause: Version has was updated before file cache
Solution: Keep all updates in one place and switch to new version at the same time

Root cause: If some of the UI containers is not available after successful start, the version update check might fail.
Solution: Add error handlers when manifests can not be fetched after startup

Fixes #6

Root cause: Due to the timeout, every request that was launched while fetching the previous manifests could led to another fetch and another cache.warmup
Solution: Be more synchronous

This prevents unnesessary large headers as the UI will filter for CSS files only

richard.petersen authored 3 years ago and julian.baeume committed 3 years ago

Includes the version string and dependencies

Signed-off-by: Julian Bäume <julian.baeume@open-xchange.com>

first hit wins. This allows us to transparently use sourcemaps and other files that
are not part of the sources according to the vite manifest

the file cache is populated with data defined in the manifest files configured for
all components and will basically fetch everything from all components. This allows
us to use this manifest service as the only source of truth for UI related sources and
simplifies ingres setup a lot.

julian.baeume authored 3 years ago and julian.baeume committed 3 years ago

this got lost when implementation changed to base data on vite manifests but should
still be part of the manifest.json file

julian.baeume authored 3 years ago and julian.baeume committed 3 years ago

those files are supposed to be downloaded directly

julian.baeume authored 3 years ago and julian.baeume committed 3 years ago

… and transform them to something that can be consumed by App Suite.