ena1106

Same issue here.

As a workaround there is the flag: `false` With this flag set the wrong params are not passed from the plugin and yarn will use the proxy settings configured in...

Thank you for the workaround! 🥳 If others are using openapi-generator-maven-plugin: - copy [dataClass.mustache](https://github.com/OpenAPITools/openapi-generator/blob/master/modules/openapi-generator/src/main/resources/kotlin-spring/dataClass.mustache) and remove (). - In the project root add a folder called `openapi-generator-templates` with the corrected...

+1. Had same issue, thank you for the workaround. I did an override in my css: `.dt .dt-body { z-index : inherit; }` But I want to know too if...

I tried @AirDur solution and it works, thanks! @mandreyel I can see the file under localhost/api.yaml. Be sure that the path ./docs/api.yaml exists, it's relative to the docker-compose.yaml file location....

Using TopicRecordNameStrategy the list of subject-schema mapping is not just long but also unreadable. AVRO AVRO It would also be nice to have a schemaType like `AVRO-IDL` to check schema...

Can you please tell me where are the AVSC files generated by the idl-protocol goal? I can only see classes under target/generated-sources/avro/classes Maybe the exec plugin was getting the schemas...

I already read that blog post. They generate avsc files with maven-exec and Avro tools library, not using the idl-protocol goal of the avro-maven-plugin.