May summary

During May the schema has been the main focus.

It's now possible to specify specific values that are valid for String field. This enables a user to select among the valid values instead of typing them in.

In the web schema editor you can now change most of the properties of fields. Previously, the editor was overly restrictive in order to prevent changes that leads to invalid existing entities. We can now enable those changes thanks to the validation changes introduced during April.

On the API side the schema is now fully normalized, so that you can always expect a consistent result after updating the schema. Schema updates are now more robust by preventing changing the type of existing fields and preventing removing existing fields. Those restrictions were previously only in the web editor but now applies to the API as well. In addition you can now do partial updates of fields, so if you don't include a property of an existing field in an update, it will keep it's previous value.

Thanks all for now!