asyncapi
[FEATURE] New release after the migration to LEGO/AsyncAPI.NET
Why do we need this improvement?
The current release (0.13.0, from March 2024) predates the migration to LEGO/AsyncAPI.NET. The readme has also been updated and is consequently out-of-sync with the current release, so the example code from the readme doesn't work as-is.
How will this change help?
Somebody using the current release (0.13.0) is unable to use the sample code from the readme without some changes (class names, properties, and constructor arguments).
Screenshots
No response
How could it be implemented/designed?
It's a breaking change that was only merged recently, so how about a prerelease NuGet package if there's still more testing to be done?
🚧 Breaking changes
Yes
👀 Have you checked for similar open issues?
- [X] I checked and didn't find a similar issue
🏢 Have you read the Contributing Guidelines?
- [X] I have read the Contributing Guidelines
Are you willing to work on this issue?
None
Hi, check this - #223. At the moment, the migration is completed, but we are not sure about the quality of our code base, after reworking the tests we will release a release.
Would a pre-release version ahead of the tests be within the realm of possibility?
