data-editible-field should validate against the block schema

[djay]

it shouldn't be possible to put fields into the block that aren't in the schema.
because all fields need to be editable in the sidebar as well.
but there also needs to be a way of easily adding custom fields into the schema

One interesting example is the teaser block. When override is set to false then the editable fields are hidden.
In this case the inline editing should be disabled?
How does hydra know?

• maybe the block should hide them and set the schema to readonly?
• or if fields are hidden then then inplace editing is always disabled?
  • but then it should be ok to customise hydra to only have inplace editing for some fields if you choose...