Open adam-codeberg opened 8 years ago
Issue may be due to using underscores in JSON relationship declerations.
Example /addressbook/schemas/contacts.jsonl Changed phone_number to phone and the issue goes away.
The above workaround works, however not sure if this is symptomatic of a deeper issue.
If a Parent model is before a Child model in the RAML the Child model is not created at the time the Parent looks for it.
Example see /contacts and /emails here /addressbook/api.raml
As a work around, the issue does not occur when the Parent is placed after the Child, however this prohibits the ability to nest objects for a more intuitive API structure.
This error is produced