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
Currently, the project uses in-house implementation of the various asyncapi types (such as Channel, Operation etc.).
This in-house implementation is problematic due to:
There are many bindings missing for most of the protocols. Actually only kafka bindings were implemented. For more plugins to be created, we need the bindings for them.
There for, it would be a great step to replace all those in-house implementations (from asyncapi/types package) with the types provided by jasyncapi-core.
Tasks
Add jasyncapi-core dependency
Replace all in-house implementations with provided types from jasyncapi. Many have the same names so the switch should be rather smooth, but I did rely on some custom builders, constructors and json serializations that may require additional attention.
Fix the tests and verify all pass
Remove local asyncapi/tests package (except for ProducerData, which may not belong there, but its future location may be decided later on).
Release local snapshot version, and update the kafka plugin. After it is updated, I will release an actual version.
The text was updated successfully, but these errors were encountered:
Motivation
Currently, the project uses in-house implementation of the various asyncapi types (such as
Channel
,Operation
etc.).This in-house implementation is problematic due to:
There for, it would be a great step to replace all those in-house implementations (from
asyncapi/types
package) with the types provided byjasyncapi-core
.Tasks
jasyncapi-core
dependencyjasyncapi
. Many have the same names so the switch should be rather smooth, but I did rely on some custom builders, constructors and json serializations that may require additional attention.asyncapi/tests
package (except forProducerData
, which may not belong there, but its future location may be decided later on).The text was updated successfully, but these errors were encountered: