Introduce serializer for spa manifest
The code for our current Spa Manifest endpoint is not aligning to DRF's mechanics. We should change this by introducing a proper serializer.
I am not quite sure though, how this should look. @wvffle Maybe you can shed some light into this?
Do we need to generate this dynamically or is it just fine to ship a static manifest json? Or the other way round, do we need the static file or is it fine to only ship it via the API? What can the manifest contain? Or what do we need it to contain?
Currently we have something like
{
"name": "front",
"short_name": "front",
"start_url": "/front/",
"display": "standalone",
"background_color": "#ffffff",
"lang": "en",
"scope": "/front/"
}
We eventually add a better short_name
, overwrite the start_url
and in case its set we also add a description
.