-
Notifications
You must be signed in to change notification settings - Fork 3
Description
Hi Mikkaello!
Great work on the repo and the improvements, really enjoying the changes!
It seems that hierarchical file structure isn't supported by the project so far. This would be a really nice improvement if possible! Unsure why it doesn't, maybe because the compiles structure doesn't happen in a given order. Below is a minimal example that doesn't work with avrodoc, but compiles and runs without problem as avro schemas.
If you have time, any insight into this would be most appreciated.
File: foo.avsc
{ "name": "Foo", "type": "record", "namespace": "example.com", "doc": "A simple object provided as a building block", "fields": [ { "name": "value", "type": "string", "doc": "The value of the object" }, { "name": "history", "type": "string", "doc": "A history field detailing random information about the object" } ] }
File: bar.avsc
{ "name": "Bar", "doc": "A complex object referencing the foo object", "namespace": "example.com", "type": "record", "fields": [ { "name": "fooObject", "type": "example.com.Foo", "doc": "A foo object" }, { "name": "name", "type": "string", "doc": "the name of the bar object" } ] }