Describe the bug.
When generating classes from multiple AsyncAPI files, I split classes into different packages. However, this creates a Config class with the same name in each package, which raises a ConflictBeanDefinitionException because they all use the same bean name 'config'.
Is there a way to handle this problem?
Expected behavior
Having different name for each bean.
Screenshots
.
How to Reproduce
.
🥦 Browser
None
👀 Have you checked for similar open issues?
🏢 Have you read the Contributing Guidelines?
Are you willing to work on this issue ?
Yes I am willing to submit a PR!
Describe the bug.
When generating classes from multiple AsyncAPI files, I split classes into different packages. However, this creates a Config class with the same name in each package, which raises a ConflictBeanDefinitionException because they all use the same bean name 'config'.
Is there a way to handle this problem?
Expected behavior
Having different name for each bean.
Screenshots
.
How to Reproduce
.
🥦 Browser
None
👀 Have you checked for similar open issues?
🏢 Have you read the Contributing Guidelines?
Are you willing to work on this issue ?
Yes I am willing to submit a PR!