-
Notifications
You must be signed in to change notification settings - Fork 9
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
fury-adapter-swagger upgrade causes Type Error #93
Comments
Thanks for opening! 👍 This is affecting me today as well. |
Could either of you please share your Swagger file (or a smaller variant that can reproduce the problem). It isn't just any Swagger document that would cause the problem. If you don't want to post it here publicly feel free to email it to me at kyle.fuller@oracle.com and I should be able to fix it shortly, the problem most likely in fury-adapter-swagger. Regards, Kyle |
Here's what makes it fail
|
Thanks @Farga83, I've prepared a fix in apiaryio/fury-adapter-swagger#120. Should get this out shortly. |
This has been fixed in the Fury adapter, but not in Dredd Transactions yet. I'm also thinking about whether it's worth writing a test, since the bug made Dredd unusable to anyone with auth in their Swagger, but there was no test to catch this either in DT or Dredd itself. |
The most recent release included an upgrade to fury and minim dependencies. With those changes I get the following error when trying to run dredd.
To reproduce, simply do a fresh install of dredd as outlined here
http://dredd.readthedocs.io/en/latest/installation.html and run dredd against a swagger.yaml file.
To work around the issue, manually update dredd/packages.json restricting the version.
I believe the commit introducing the issue is ea91dc6
The text was updated successfully, but these errors were encountered: