It looks, that currently Spinta checks enum values on read, but that should not be doen. Enum values should be checked on write.
Disable current checks on read and add checks on write.
This might cause a lot of issues, with existing integrations, so before releasing this, we also need to check Saugykla, if there are any incorrect enum values, contact all data providers, fix data, and only then, when all enum values are correct, release enum value checks on write.
It looks, that currently Spinta checks enum values on read, but that should not be doen. Enum values should be checked on write.
Disable current checks on read and add checks on write.
This might cause a lot of issues, with existing integrations, so before releasing this, we also need to check Saugykla, if there are any incorrect enum values, contact all data providers, fix data, and only then, when all enum values are correct, release enum value checks on write.
Related