Michael Bangert

Separating this out like with the attribute_functions makes sense to me. Note that based on the comment in #499 about not parsing location from metadata the path for `openapi_location ==...

This part of `fields2parameters` won't be needed either: https://github.com/marshmallow-code/apispec/blob/15a06ebcc346d4ed1aa47e41b7a939393d7b9445/src/apispec/ext/marshmallow/openapi.py#L169-L182

The one reason to leave it public is that currently apispec does not handle webargs arguments defined as a dictionary of name, field pairs. The tests calling `fields2parameter` are basically...

The marshmallow plugin is not looking for marshmallow schemas nested within properties of a schema defined in a YAML. You can solve this two ways: 1. Use your manual binding...

@lafrech were you thinking of including custom attribute functions in apispec? It might be convenient to include them in the same repo as the custom field so that they could...

My expectation is that many/all of the custom attribute functions are going to depend on the custom field because the most convenient way to write them is to test if...

In most cases you should not rely on `get_unique_schema_name` to provide names for schemas using modifiers. This function is provided as a fall back to ensure that the generated spec...

@Sinclert To avoid registering nested schemas, you can pass a `schema_name_resolver` that always returns `None`. If you do this you cannot have circular references in your schemas. My opinion is...

The documentation under the Nested Schema documentation you reference includes this sentence: > If the schema_name_resolver function returns a value that evaluates to False in a boolean context the nested...

How about adding an [extension](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#specification-extensions) to indicate the order to the user. Maybe something like: ```json { "type": "array", "items": { "oneOf": [ {"type": "number"}, {"type": "string"} ] }, "minItems":...