Description
Reason/Context
I am a frequent user of OpenAPI and use NSwag extensively to manage REST API integrations. NSwag has the ability to customize namespaces, data structures, and output file structure, which is a significant benefit. However, the dotnet-rabbitmq-template project lacks this extensibility feature. Therefore, I would like to request this feature to enhance the dotnet-rabbitmq-template project's productivity and flexibility for AsyncAPI developers in a .NET environment.
Description
To implement this feature, the dotnet-rabbitmq-template project needs to be extended to allow for customization of namespaces, data structures, and output file structure. This change may potentially remove the csproj, appsettings, and other files, which would require more setup by a user to get a working application. As a result, this feature could be considered a breaking change.
To overcome this issue, a migration guide and documentation should be created to help users transition smoothly to the new version of the project. Additionally, backward compatibility could be maintained in the current version of the project for users who do not wish to migrate to the new version.
How will this change help?
This feature will allow users to customize namespaces, data structures, and output file structure to fit their specific requirements. This flexibility will make the dotnet-rabbitmq-template project more useful as a production tool for AsyncAPI developers in a .NET environment.
Motivation
As a heavy user of OpenAPI and NSwag, I believe this feature will provide a significant benefit to the project's productivity and flexibility for AsyncAPI developers. The ability to customize namespaces, data structures, and output file structure to fit specific needs will make the project more useful and applicable to a broader range of users.