Laurent Broudoux
Laurent Broudoux
I did some quick tests, and it appears that the latest `1.4.x` release of the component supports the `2.6.0` version of the spec, but it fails to render previous versions...
Hey @AceTheCreator I've done some complementary tests and have found some interesting results... It seems that the `1.4.5` version of the components behaves a bit differently on examples rendering depending...
Ok but as I understand, it means that it may then break v3 document representation that holds functions once the spectral rules are ported to v3... It could be nice...
Could you please reference here the linked issue on AsyncAPI web component? That way it'll be easier to track.
Hey @AceTheCreator! Is there any update on this one on the AsyncAPI Web component side? Didn't check the releases recently... do you have any hints?
Need some extra checks to see how to integrated fix from web components and what are the consequence on Microcks side.
Hey @AceTheCreator, I updated to the latest `2.5.0` versions of both the `@asyncapi/web-component` and the `@asyncapi/react-component` and still have issues with documents with a version before 2.6. Typically, the document...
Good idea! Project was started JUnit4 a loonng time ago but can definitely switch to JUnit 5. Issue can be split into more focused ones attached to this main one...
Now done. Thanks to @gbloquel for awesome contrib!
Reopening this one as we still encountering issues in https://github.com/microcks/microcks/pull/1210. Maven Surefire plugin version used should be more deterministic.