Bad form replying to my own response, but i have inspected it some more and have some comments.
1. The site says schema.org is included, but schema.org is mainly just documentation, I woukd like something more like json-schema that I can actualy use the schema data directly.
2. I dont get why the validators have function names, surely the validator is anonymous, and its name should be a function of the property path, the argumant is always "value", and it always returns a boolean. So why do you need to declare a name at all.
3. If you cant support json-schema then you need an export function that allows you to export valid draft v8 json-schema.
4. Some way of anotating properties for graphql endpoint generation would be cool, ie generating .graphql files, or mongodb bson.
1. The site says schema.org is included, but schema.org is mainly just documentation, I woukd like something more like json-schema that I can actualy use the schema data directly.
2. I dont get why the validators have function names, surely the validator is anonymous, and its name should be a function of the property path, the argumant is always "value", and it always returns a boolean. So why do you need to declare a name at all.
3. If you cant support json-schema then you need an export function that allows you to export valid draft v8 json-schema.
4. Some way of anotating properties for graphql endpoint generation would be cool, ie generating .graphql files, or mongodb bson.