Actions with colons in the URL path experience a parse issue

[morganebridges]

Example:

/audience_experts:query:
    post:
      operationId: audience_experts:query_create
      description: Query audience_experts across projects
      parameters:
      - in: query
        name: format
        schema:
          type: string
          enum:
          - csv
          - json
 
We don't have any problem generating and using the openapi schema in other contexts. I don't think there is anything explicitly dis-allowing usage of colons in the path, and some projects I work on use them to denote a non/restful "action" at a particular resource root.

What do you think?