Replies: 1 comment
-
We had considered something "tuple"-related as a name for The intent for the keyword is that you could have any ordered set of different types. While tuples are a common use case, they're not the only one, and so naming it "tuple" isn't general enough. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
After many years using the draft-07, my employer decided to update to draft 2020-12. One confusing thing that truly strike about this draft version is the introduction of the prefixItems and items for tuple, which is confusing, mainly when maintaining the schema.
My suggestion is rather than introducing new keywords, why not simply introduce a new type tuple?
For one, the true intention is clear, an array containing different type, for two, the word tuple is recognized in the IT community and would not cause any confusion if introduced.
Beta Was this translation helpful? Give feedback.
All reactions