Jérôme Lafréchoux

Change released in 6.0.0b1.

Does it work if you register mini bar schema like this first? ```py spec.components.schema("MiniBarSchema", BarSchema(only=("id", "name"))) ```

Also, if you register `BarSchema` (real one) first, you should only get a warning, not an error, when the mini one is auto-registered.

> There should be a way to easily configure name generation That is `schema_name_resolver`. It is a somewhat advanced feature, indeed. But apispec can't reasonably define automatic names for modified...

apispec respects schema order. You may want to double-check your code doesn't force alphabetical order (for instance, by default, Flask sorts keys when serializing json).

Closing for lack of feedback. Free free to bring additional details in comments.

Technically, the fix is a breaking change. We can do it in next major. No rush because it is currently just a deprecation warning. It is in the TODO list...

Yes! Absolutely. Would you like to submit the change?

Since it may contain nested fields, it probably deserves a special treatment in there like `List` and `Dict`: https://github.com/marshmallow-code/apispec/blob/dev/apispec/ext/marshmallow/openapi.py#L420. There's been discussions in https://github.com/marshmallow-code/apispec/issues/172 about making this easier to extend,...

Info about representing tuple in OpenAPI: - https://json-schema.org/understanding-json-schema/reference/array.html#tuple-validation - https://stackoverflow.com/questions/57464633/how-to-define-a-json-array-with-concrete-item-definition-for-every-index-i-e-a I'd like a solution here that doesn't try to handle older OpenAPI versions.