Why am I still hand-typing WebSocket structs from an AsyncAPI spec?
You shouldn’t be, because the AsyncAPI spec already says exactly what every message looks like and a machine can retype it better than you. I wrote gen-asyncapi so an AsyncAPI …
Mostly writing code that does stuff…
You shouldn’t be, because the AsyncAPI spec already says exactly what every message looks like and a machine can retype it better than you. I wrote gen-asyncapi so an AsyncAPI …
These are the lines the whole project exists to run. Everything else in docker-mql-compiler is setup for them, or cleanup after them: # MetaEditor’s exit code is backwards (1 usually …
Look, if you’ve ever wasted more than 5 minutes trying to hunt down which structs actually implement a Go interface, you already know this pain. It’s like trying to debug …