Dave Koston

Apologies, this seems to be an error in my code related to using channels with the new API. If I remove the channels from the above code it works to...

@fehguy without supporting this in the spec, it won't make it upstream into all the consumers of OpenAPI. For example, I use google cloud endpoints and they don't support `private`...

@MikeRalphson the attempt here is not security by obscurity. If people aren't defining security for endpoints they want to have hidden from documentation/tools, that's a huge mistake and could cause...

> Unless there is some consensus on what "treated differently" means, by the tooling providers, I think this idea is so vaguely-defined as to be unlikely to be adopted by...

@webron Thanks for the clarity. Seems like pre-processing and/or Overlays is the approach to take when features aren't supported by the core spec.

@manchenkoff no problem. I realized I used too old of a poetry version. Pushed fix. Will keep an eye on the build. Have a PR coming that allows all IANA...

Just an FYI that I've confirmed this fixes routing bugs in connexion that exist today. For example, attempt to add these 2 routes: ``` paths: /users/{user_id}: get: /users/accept: get: ```...

@RobbeSneyders is there any documentation on how to run the test suite? I added some tests but running the lines from [.github/workflows/pipline.yml](.github/workflows/pipline.yml) results in almost all tests failing even though...

> @RobbeSneyders is there any documentation on how to run the test suite? > > I added some tests but running the lines from [.github/workflows/pipline.yml](.github/workflows/pipline.yml) results in almost all tests...

`v3.4.0` has the same issue. It appears that these updates are not backwards compatible / have bugs with cache`path`