Vladimír Gorej

> Hmm, I see I haven't formulated myself well enough in the article. One of the points it's missing is a deeper explanation of the schemaFormat. When you define it...

[PR](https://github.com/asyncapi/spec/pull/777) has been issued for [next-major-spec](https://github.com/asyncapi/spec/tree/next-major-spec) branch.

> I would then like to suggest we do it on the spec document I guess that's automatically implied that specification itself is the single source of truth. Would be...

> I believe most users (including potential ones) won't read the README file, but rather navigate through the AsyncAPI website. Just an idea: how about mentioning it in README and...

@smoya ahh sorry I misunderstood. I've issued a PR to the website adding the sentence there as well: https://github.com/asyncapi/website/pull/743

I confirm, it's been merged into master as editorial change - https://github.com/asyncapi/spec/commit/02393d166a5c70481bd2f7f7f23d69c4f24b83b1

Hi guys, I've looked into the [Vite.js](https://vitejs.dev/) briefly and here are my observations: - Vite is based on [rullup](https://rollupjs.org/) - Vite is also based on [esbuild](https://github.com/evanw/esbuild) - Vite allows to...

> Yet - I'd argue that removing dependencies is a good thing. If we don't really need the dependency on `"buffer"` _and_ it causes problems, why keep it? From a...

I've produces https://github.com/swagger-api/swagger-ui/pull/7946 that deals with Node.js polyfills and other problems in main SwaggerUI fragment. If you continue with this PR, please pay attention also to webpack config in the...

Hi guys, As mentioned in https://swagger.io/blog/api-design/what%E2%80%99s-ahead-for-swaggerui-v4-and-swaggereditor-v4/, 4.x release is the first step of OAS 3.1 adoption.