mleku on Nostr: humbug i thought i'd written a correct openapi spec to include the insane nip-11 ...
humbug
i thought i'd written a correct openapi spec to include the insane nip-11 structure that you may recall me commenting on it's insane dynamic unstructured array specification
the editor was happy, so was the swagger UI generator and so was the UI generator built into intellij
but the actual code generator, the most popular and extensive one shits the bed with some whine about some part of that insane structure being missing a schema
so, i actually am very annoyed that i wasted my time completing that specification as i did yesterday, even though supposedly it was valid, it was not valid according to my generator
probably some versioning problem with some feature my generator doesn't understand
it thinks it's perfectly complient with even 3.0.0 but the oapi-codegen doesn't agree
oh well, screw it, truth be told that stupid data structure doesn't parse properly into Go semantics without inordinate amounts of interface boilerplate so idgaf, screw your dynamic type tomfoolery, i am ignoring your stupidity
instead, i am going to just supersede this stupidity with a sane system of defining APIs like the rest of the entire world is doing outside of nostr dev
i thought i'd written a correct openapi spec to include the insane nip-11 structure that you may recall me commenting on it's insane dynamic unstructured array specification
the editor was happy, so was the swagger UI generator and so was the UI generator built into intellij
but the actual code generator, the most popular and extensive one shits the bed with some whine about some part of that insane structure being missing a schema
so, i actually am very annoyed that i wasted my time completing that specification as i did yesterday, even though supposedly it was valid, it was not valid according to my generator
probably some versioning problem with some feature my generator doesn't understand
it thinks it's perfectly complient with even 3.0.0 but the oapi-codegen doesn't agree
oh well, screw it, truth be told that stupid data structure doesn't parse properly into Go semantics without inordinate amounts of interface boilerplate so idgaf, screw your dynamic type tomfoolery, i am ignoring your stupidity
instead, i am going to just supersede this stupidity with a sane system of defining APIs like the rest of the entire world is doing outside of nostr dev