-
Notifications
You must be signed in to change notification settings - Fork 9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Model Schema only resolves first of multiple properties with same model #245
Comments
that looks like a bug from what you posted. As a test, can you change |
|
OK, sounds like the schema view is only allowing a single instance of an object. I can see cases for and against that behavior but here, it seems to be doing the wrong thing |
I was under the impression that this change was done to avoid infinite recursion (where Model X contains an X in a property). The fix is a 1-liner in swagger.js file. Note: The only file that really changed in the above was swagger.coffee, the rest of the changes were because I am using a different version of the node coffee compiler. |
this is pushed to master. |
Hi,
I'm writing some custom models for my API. I have a Colour_pure_and_tinted model, which holds 2 properties of the model "Colour", each is the representation of either unaltered pure RGB values or manipulated ones:
But in the Model Schema view, only the very first instance of Colour (property "pure") is resolved to its proper atomic properties representation. "tinted" remains as just "Colour":
Am I doing something incorrectly or is this a bug?
The text was updated successfully, but these errors were encountered: