Support object and definitions in same file about json-schema-to-elm HOT 4 CLOSED

Hmm, your schema file looks fine, so slightly odd that I haven't noticed this issue before.
What happens if you remove the id property from the color definition?
Nonetheless this clearly seems to be a bug and I will investigate the issue.

from json-schema-to-elm.

If I remove the id I get only one name collision

--- NAME COLLISION ------------------------------------ examples/wine/wine.json

Found more than one property with identifier '#/definitions/color'

from json-schema-to-elm.

Okay, I think the error happens because the parser flattens the tree structure of the JSON schema object into a map of json pointers to type definitions (e.g.

%{
  "#/properties/color" => %TypeReference{...},
  "#/definitions/color" => %EnumType{...}
}

and perhaps an unintended clash happens between the definition of color and the reference to color.

Btw, if you want to dig deeper into this, you can build the script with MIX_ENV=dev mix build, which should make it print out a lot of debugging information when you run ./js2e ... If not, I will also be looking into this shortly.

from json-schema-to-elm.

Yes, I'll take a look at the code

from json-schema-to-elm.