Justin Black

So our code + use cases to add imports is a nest of spaghetti. There are many import addition call sites and they behave differently. The general cases are: ```...

Related: https://github.com/OpenAPITools/openapi-generator/pull/13056

@mikeknep can you make a separate issue for that? The property that you mention is a codegenProperty whereas the one that I am mentioning is a codegenModel so they work...

`python` (`python-experimental` before 6.2.0) Development of this generator is continuing in [this different repo](https://github.com/openapi-json-schema-tools/openapi-json-schema-generator) Update: openapi v3.1.0 document ingestion is supported in the new repo and includes these new/updated keywords:...

Any adjacent keyword will work. Including vendor extensions if we process them. It looks like we need a vendor extension property added to our IJsonSchemaValidationProperties interface. I have made an...

If the additional properties are not defined in the source schema and your source schema defines additionalProperties as false, then that schema is saying any additional properties are not allowed...

> it is agianst the design intention Yes your suggestion is against the intentions of json schema.

Here are the docs on our mustache template library: https://github.com/spullara/mustache.java Here are some docs on how mustache is used: http://mustache.github.io/mustache.5.html Please read through the FastAPI generator here: https://github.com/OpenAPITools/openapi-generator/blob/master/modules/openapi-generator/src/main/java/org/openapitools/codegen/languages/PythonFastAPIServerCodegen.java#L130 It processes...

Nope. Enums are fully working in `python-experimental` though, how about trying it? Or would you like to file a PR fixing `python-fastapi`? One can see enums working in `python-experimental` in...

Using the newest version is not possible because it crashes when specs with version 3.0.X. These bugs are blocking: - https://github.com/swagger-api/swagger-parser/issues/1783 - https://github.com/swagger-api/swagger-parser/issues/1781