4 ms·
I imagine you are very much in the minority. A simple hello world is like a screen full of yaml. The equivalent in graphql (or typespec which I always wanted to
by WickyNilliams 10mo ago
I imagine you are very much in the minority. A simple hello world is like a screen full of yaml. The equivalent in graphql (or typespec which I always wanted to try as an authoring format for openapi https://typespec.io/ https://typespec.io/) would be a few lines
- 0x696C6961 10mo agoBeing verbose doesn't make it difficult.
- WickyNilliams 10mo agoNot necessarily, no. But at a certain point, I believe it does. Difficult to read, is difficult to edit, is difficult to work with. A sibling comment to your reply expressed the same sentiment as me, and also mentioned typespec as a possible solution
- makeitdouble 10mo agoI see your point, yet writing openapi specs by hand is pretty common. There is the part where dealing with another tool isn't much worth it most of the time, and the other side where we're already reading/writing screens of yaml or yaml like docs all the time. Taking time to properly think about and define an entry point is reasonable enough.
- btreecat 10mo agoThe standard pattern in go and some scala libs, is to define the spec and generate the code. I think you're over fitting your own experiences.