Closed chuwy closed 6 years ago
I think it'd make sense to externalize it to a different repo as it can be useful to people not using iglu at all, I created https://github.com/snowplow-incubator/json-schema-gen as a placeholder (we can definitely find a better name)
I have few counter-arguments (though I definitely prefer multi-repos):
I say keep it here for speed of development. It can always be moved out (orchid pattern) later if it's useful.
It will depend on Schema DDL through JSON Schema AST and therefore several other Iglu libs (Scala Core at least)
why does this make having it in this repo mandatory?
I was planning to add Iglu Client shortcuts to generate schemas out of remote registries
same as above. Additionally this seems a bit out of the original scope to me. It'd better fit as a submodule, wdyt?
I'd argue that incorporating it to this repo will completely prevent wide-spread usage (SEO will be awful).
I'd argue that incorporating it to this repo will completely prevent wide-spread usage (SEO will be awful).
That's not in any way our priority though. Our priority is launching a BigQuery Loader for GCP - whatever is faster to that end.
why does this make having it in this repo mandatory?
Not mandatory at all. It was the point regarding people not using Iglu - there will be huge part of Iglu anyway. As of actual repo - ok, I'm moving it to same https://github.com/snowplow-incubator/json-schema-gen, I think it will be faster to keep it out of main repo.
...or actually https://github.com/snowplow-incubator/scalacheck-schema
scalacheck-schema
Nice name
scalacheck-schema-ddl
is a module responsible for generating self-describing JSON instances out of JSON Schemas. It hasschema-ddl
in name because it leverages typesafe JSON Schema AST from Schema DDL project./cc @BenFradet @asoltysik