COMS Micro-Frontends 1.3.0
| MFE Tag | Description | Version select | Open testpage for version | Open documentation |
|---|---|---|---|---|
| tef-coms | COMS micro-frontend for customers. | Test page | Documentation | |
| tef-coms4cs | COMS micro-frontend for customer service. | Test page | Documentation | |
| tef-coms4cs4p | COMS micro-frontend for customer service for kernel consents (fka 4th-platform). | Test page | Documentation | |
| tef-coms4p | COMS Micro-frontend for customer self-service of kernel consents (4p). | Test page | Documentation |
Technical details
The URLs to all static assets have the structure /{component}/{version}/{asset*},
e.g., /tef-coms/v2/tef-coms.js.
{component} is the name of the custom element (equals the name of the npm package),
i.e., tef-coms or tef-coms4cs.
{version} is either a SemVer-compliant full version,
e.g., v2.0.0 or v3.0.0-beta.1.
Or it is an unspecific version, e.g., v2 or v2.1 or latest, which is redirected
to the highest matching specific version (http status code 302),
if available, first matching stable versions, second matching prerelease versions.
When referring to static assets, e.g, in an html <script> tag,
please make sure to refer to major versions only, e.g., /tef-coms/v2/tef-coms.js,
to automatically update to new patch and minor versions.
All static assets are configured to be cached by the browser or any other cache
for 1 hour (see cache-control headers).