-
Notifications
You must be signed in to change notification settings - Fork 76
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
$ref pointing to a external file #60
Comments
I would love to have support for this. Are you interested in doing it, or On Thu, Feb 26, 2015, 7:17 AM Roselma Mendes [email protected]
|
Hey, Thanks for your answer. |
Awesome. I look forward to it. Here are a few things that might be useful for you.
|
This feature is now going to be much easier to implement. There is some research I still need to do in how to resolve what url should be used (if any) for things like this. |
Is it still not implemented? |
This is not implemented and you have my full support in working on this if you so choose. Any implementation that actually fetches resources from an external URL makes me a little nervous but I'm not sure that concern is well founded. I think it's safe to proceed as if it isn't an issue and we can assess whether there is any security concern. |
Hi! I need a help. Is there a one place where I can patch $ref resolving with external path? May be it would be better to create a separate module for $ref resolving and invoke it from any place where it is needed? Thank you! |
I am wondering if flex accept to use $ref pointing to an external file.
In the Swagger documentation say:
parts of the definitions can be split into separate files, at the discretion of the user. This is applicable for $ref fields in the specification as follows from the JSON Schema definitions.
Calling Flex, I tried to use json specifications, like:
or following the Flex specifications to reference definitions. Without "definitions" word.
I get this:
account_swagger.yaml#/Account
'Is this possible implement on the Flex?
Does it worth do this?
Thanks.
The text was updated successfully, but these errors were encountered: