We are going to make those fields non-multilang. This requires work in multiple repos and the deployment must be done in sync:
old laji api
old Kotka frontend
new kotka frontend
laji.fi
Because the deployment must be done in sync, the code changes to each repo should be done in a separate branch, so normal deployment can continue while waiting for the migration operation.
WHY THE HACK?
There's some historical, hypothetical reason for this hack this that was never implemented.
WHY FIX IT?
The hack creates discord between our schema and front-ends - schema says one thing while API says another thing.
These fields are multilang in our schema. api.laji.fi transform them into strings using "en" lang, and all front-ends treat them as non-multilang:
We are going to make those fields non-multilang. This requires work in multiple repos and the deployment must be done in sync:
Because the deployment must be done in sync, the code changes to each repo should be done in a separate branch, so normal deployment can continue while waiting for the migration operation.
WHY THE HACK?
There's some historical, hypothetical reason for this hack this that was never implemented.
WHY FIX IT?
The hack creates discord between our schema and front-ends - schema says one thing while API says another thing.