I noticed an undocumented behavior with listeners, where some of them run in reverse order of registration

1. What is the rationale for that?
2. Can this be added to the docs?

Additional context
Relevant lines of code from https://github.com/huge-success/sanic/blob/master/sanic/app.py#L1356

 # -------------------------------------------- #
        # Register start/stop e

Other codegen tools support circular references. See swagger-api/swagger-codegen#728.

I this this issue with the following yml:

  Node:
    description: Generic node.
    type: object
    properties:
      type:
        description: Type or label of the node.
        type: string
      properties:
        description: Node specific dictionary of key/value pairs

Adding examples responses.
I see there is a method to add responses @doc.response but is there a method to add example responses?

It would be nice if @doc.example() added example code to the OpenApi spec.

Slightly related question
Is there a way to populate the Example Value box with a real example, or will that only

Reading the Sanic JWT docs, although override_scope_validator is mentioned in Initialization and it mentions See Scopes for more information., override_scope_validator seems to be missing in Scopes.

Based on your documentation, I should be able to force sanic-cors to show only logs at INFO level like this:

cors = CORS(app, resources={r"/static/*": {"origins": "*"}})
logging.getLogger('sanic_cors').level = logging.INFO

This works if the logging level for the app is also set to logging.INFO, but as soon as the app’s log level is set to logging.DEBUG, even with the sec