Vladimír Gorej

After thorough testing I can say that new grammar is mostly compatible with what we need in ApiDOM. Node.js bindings and compiled WASM integrates with other tree-sitter libraries. One incompatibility...

There is a new YAML tree-sitter grammar being worked on. This issue will be addressed there. More info in https://github.com/swagger-api/apidom/issues/4033

Additional notes: After further research I've come into the conclusion (**subjective one**), that It's currently really not worth the effort. If we would like to switch to TypeScript mixins we...

Thinking further...what we can do is to identify packages where using stamps is not really necessary. We really only need stamps for facilitating multiple inheritance which is not natively supported...

Another package that has been identified is https://github.com/swagger-api/apidom/tree/main/packages/apidom-ast All the AST node types can be represented as TypeScript classes as there isn't multiple inheritance involved.

We already bumped into issue of breaking the backward compatibility. To avoid breaking the compatibility mainly with (swagger-client) we would utilize following strategy for the time being: > [!IMPORTANT] >...

Work is currently being done on `apidom-ns-workflows-1` package. Withing the package there is one stamp that's being composed to new stamp. We will do the following conversion to get rid...

API Design Systems namespaces has been addressed as first namespace package and as a POC in https://github.com/swagger-api/apidom/pull/3704. It didn't have any other namespace packages as dependencies so it was simpler...

Current plan is to finish this, create breaking changes, fully get rid of `stamps` and release `v1.0.0-alpha.1`

Finalized in https://github.com/swagger-api/apidom/pull/4105