As detailed in #14, JSON schemas enums can be any JSON value, while AVRO limits its enums to string tokens.
Implement a translation for non-string JSON schema enums.
Open questions:
What kind of AVRO type could this be translated to?
Is it even possible to specify arbitrary JSON values to validate against in AVRO?
If not, do we need to infer a schema from a value? That seems like a non-trivial effort.
As detailed in #14, JSON schemas enums can be any JSON value, while AVRO limits its enums to string tokens. Implement a translation for non-string JSON schema enums.
Open questions: