This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of swagger-ui.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
5da72aachanges to prevent the parameter description column from expanding (e.g. due to very long words in the content that cannot wrap). the new behaviour is that the long content just spills into the adjacent column.
38f7416Merge pull request #2612 from oprince/master
With Integrationsfirst-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever.
Screencast Try it today. Free for private repositories during beta.
Hello lovely humans,
swagger-ui just published its new version 3.0.0.
This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of swagger-ui. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project :sparkles:
You rock!
:palm_tree:
The new version differs by 23 commits .
373ea3cBuild core onlye57b6abAdd travis and npm stufff22a628in with the newbd8344cout with the oldccf7f03Merge pull request #2677 from banders/param-descriptions-cutoff61d5e98Merge pull request #2701 from jessemcdowell-AI/patch-191381ffPoint 2.2.10 tag url to correct tag0beaf61Merge pull request #2691 from hochzehn/docker-exitableb2e313fAttach nginx process to PID 1 so the container can be stopped properly.6f1b09eMerge pull request #2685 from scottohara/json-editor-v0.7.28911b9e0Update jsoneditor from v0.7.22 to v0.7.28 (Fixes #2659)3b4cbebMerge pull request #2684 from stephendonner/typos0993e78Minor typo fixes5da72aachanges to prevent the parameter description column from expanding (e.g. due to very long words in the content that cannot wrap). the new behaviour is that the long content just spills into the adjacent column.38f7416Merge pull request #2612 from oprince/masterThere are 23 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.