Closed yurvon-screamo closed 4 months ago
that's great news! just as a little info, there is already a package called AsyncApi.Net from Lego, so you might consider a different name to avoid confusion:
that's great news! just as a little info, there is already a package called AsyncApi.Net from Lego, so you might consider a different name to avoid confusion:
Lego package is asyncapi dto + serializer, my package is document generator. + I'm thinking of rewriting the library using the lego package, then it will be a great addition and the postfix will be useful)
I agree that this (the generator package) should use the base AsyncAPI.NET package from Lego.
The fork looks fine, but I'm not really sure it's mergable with all the namespace and file path changes.
What would you like to do with this fork?
I agree that this (the generator package) should use the base AsyncAPI.NET package from Lego.
The fork looks fine, but I'm not really sure it's mergable with all the namespace and file path changes.
What would you like to do with this fork?
The purpose of my work is very simple - to make a workable library that will close the tasks assigned to my team.
I'm not suggesting we merge our versions. The request pool was created more for information purposes.
Hello, i`m rewrite saunter and ready to maintenance and support new version.
link
Additionaly - created pull requests, if current repo maintenaner are interested
Self roadmap list:
The main purpose of the stage works is to make it possible to describe an operation in 1 attribute without restrictions on the number of operations per method/class
[X] To dotnet 7
[X] To asyncapi 2.6.0
[X] Set required and nullable props to schema
[X] Give the opportunity to work with multiple operations in the one class/method
[X] Kill channel attribute:
[X] Rework message attribute:
[X] Kill channel params attribute (auto detect parameters from channel name)
[X] Redo the processing of multiple documents in the application (save default document with
null
name!!)[X] Rewrite usage docs:
[X] Nuget package
[X] Usability test on my environment Based on the results of the check in my environment. Using the library has become much more convenient, but there is not enough flexibility in implementation. Next, I will develop the library towards tools WITHOUT attributes. Example case:
[X] Release !!
Known limitations of the version that will be received at this stage: