Certain fields are required by Statamic and when they are deleted Statamic ignores that you deleted them and saves the blueprint after adding the fields that were just deleted.
This is rather confusing; a better experience might be to disable the delete button entirely on these fields.
Could also extend this idea to have certain defaults that can't be overridden (ie. make it so one cannot remove the "required" validation on a slug field and disable the handle field on a slug)
Examples I can think of:
slug
taxonomy (when associated with the parent collection)
Certain fields are required by Statamic and when they are deleted Statamic ignores that you deleted them and saves the blueprint after adding the fields that were just deleted.
This is rather confusing; a better experience might be to disable the delete button entirely on these fields. Could also extend this idea to have certain defaults that can't be overridden (ie. make it so one cannot remove the "required" validation on a slug field and disable the handle field on a slug)
Examples I can think of: