untyped, unstructured JSON arrays are the devil

to express them in openapi you have to define them in components and combine them to make them work properly

i am really wasting a lot of time addressing this lunacy in the retention field of nip-11 on this, like, how do i... ok, it's this "oneOf" shit

i am appalled at how unnecessarily complex this is, and the fact that i'm editing the spec on a runtime environment that is executing this lexical analysis and static syntax checking inside an abominably poorly designed interpreter engine instead of a fucking at least bytecode interpreter, it takes it like 7 seconds to parse the grammar of edits i make sometimes