Feature/798 swagger viewer error check, closes #798 #845
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I suppose this closes #841 as well, if it works. Deployed this branch to nightly.apinf.io and error has disappeared, because this exception happened only in production instances. |
|
Traced the error with @brylie Now able to produce error locally as well. Problem is with the data context. We have subscribed to ApiDocs, but not to ApiBackends user does not have rights to manage. |
|
@apinf/developers please review |
# Conflicts: # lib/i18n/en.i18n.json
|
Tested, good work 👍 |
frenchbread
added a commit
that referenced
this pull request
Feb 9, 2016
…heck Feature/798 swagger viewer error check, closes #798
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.