Respect required fields for required property mapping

In principle, I agree with this. However, I am not sure that requiring a default value is a high bar to set. Specially since this is a site building task, that you won't do that often. I am thinking about entities that are created without a form (programmatically, or via JSON:API, etc.). Drupal still does much of the data validation through forms.

Drupal still does much of the data validation through forms.

We're working to change that :) See 🌱 [meta] Add constraints to all config entity types Active in particular and 🌱 [meta] Config validation for a more reliable Drupal + reliable Recipes from the start Active in general :)