Making progress in #auralis for the #openapi plugin implementation, but looks like I have a long way before me.
I also might need to switch from the `:param` syntax to `{param}`, because this is what the default for OpenAPI spec is. Also this is how Spring is doing it.
But need to think about that a bit.
I started drafting a plugin system for #Auralis 🧩
As a first plugin I plan to publish `@auralis/openapi`
I took inspirations from #NestJS, #Vue, #Vite and other systems. Usually I try first to write the code a consumer of auralis would write and then implement the stuff behind it.
Next step: find a nice lib to generate the json/yml spec response.
I know it's a small thing, but #auralis has a `README.md` now in the core package 
Also since last post I added `@Request` and `@Response` param-decorators, so now you can go more crazy and set your own headers or manage your own body response and stuff like that.
But I plan to add decorators for adding headers, response code and stuff like that. ✨
For now my next plan is to look into testability 🧪
https://github.com/auralisjs/auralis/blob/main/packages/core/README.md
My new project #Auralis is now already published on #npm
https://www.npmjs.com/package/@auralis/core
Sure there is no documentation or anything else yet, but you can try to explore the example in https://github.com/auralisjs/auralis
If you have any feedback or ideas or even want to contribute, then just come over and use the #GitHub Discussions, Issues or Pull Request 
Shini92
王永帥🍥