forked from swagger-api/swagger-ui
-
Notifications
You must be signed in to change notification settings - Fork 2
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
Start development of v21 based on swagger-ui@v2.1 #7
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
…robust to potential HTML tags cannot be nested within the <p> context.
OperationView.js: fix rendering of Markdown (GFM) in description fields.
Fix typos in SwaggerUi.js
Fix swagger-api#1040 : add options to be able to sort APIs and operations
Make SwaggerUi UMD compatible
…turl Add ability to override redirectUrl in swagger-oauth
Original code didn't work because of a mix between the use of 'apisSorters' and 'apisSorter' references. Changed all 'apisSorters' refs to 'apisSorter'.
* Uses npm to download latest swagger-js (for now. When swagger-js is released we will replace git address with actual swagger-ui) * Uses `postinstall` to generate `browser` folder of swagger-ui. This can go when swagger-ui is published.
Use SwaggerJS from npm
xit out tests that are failing due to SwaggerJS
Fixing sorter typo
Add file download to try operation
swagger-client@2.1.0-M2.alpha2 need to get published for this
Cleanup package.json
Add support for oauth client secret when calling the token URL. Fixes swagger-api#1384. Fixes swagger-api#1324.
…s-detection Fix validator's https detection
Missing some data-sw-translation
Prepare for release
bajtos
added a commit
that referenced
this pull request
Aug 6, 2015
Start development of v21 based on swagger-ui@v2.1
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.
Merge v2.1.1 from swagger-api/swagger-ui. This is a breaking change that reverts all custom enhancements implemented by this module on top of swagger-ui@v2.0.x.
Drop bower support - we don't need bower for loopback-explorer, plus bower does not support compiled distributions.
Connect to strongloop-internal/scrum-loopback#412
Connect to strongloop/loopback-component-explorer#54