RFC: Propagate `unknown` value through nested schemas?

I’m wondering if the unknown value set on parent schema should propagate down through all nested schemas.

We raise by default, and to change that, one needs to let all his schemas specify another behaviour (~this is broken but will be fixed when #963 is merged~). This can be done with a custom schema to use as a base for all schemas, so it is feasible, and raise is a sensible default IMHO, but wouldn’t it make sense to let the parent schema unknown setting propagate?

[zaraken]

For now, our stance is that class Meta options should not be automatically propagated to nested fields. Users should use an base schema class in order to share default options across classes.

I do agree that class Meta options should not be automatically propagated.

However, what about when overriding unknown in the load method which should according to documentation override the value set at instantiation or in Meta. For this use case it would make sense to (conditionally) allow propagation to nested fields or ?

[charlax]

At the very least, this behavior should be documented.