You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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'.
Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request. Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.
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!
The text was updated successfully, but these errors were encountered: