Just updated coverage.#399
Conversation
…t one version." This reverts commit 5173d9f.
|
Eeeek. Some confusion here on my part. A gem should not show up in just updated if it's a brand new gem with it's first version. Updating the cucumber scenario to reflect this. We do run into an interesting scenario however, where a new gem, once it has two versions released, will show it's first version in the just updated section incorrectly (if there's a small number of gems, which is not a realistic case, or the window of time between releases is small). The correct behavior of just updated in this case would be to show only gems with more than one version, with it's first version excluded. Sound correct? |
|
That bit sounds correct. Does this account for cases like this one for the launchy gem: I kind of think you'd want both of these appearing. |
|
Merging for existing coverage before changing it. |
5.0.0 / 2016-11-05 Major enhancements Cleanup deprecated code targeted Ruby 1.8 Bug fixes Ensure badge data is included in result of JsonIndex template. Ensure items in the nil section are displayed in HTML output. Issue #399 by Daniel Svensson. Parse rb_intern_const correctly in C. PR #381 by Sho Hashimoto. Fix broken assets caused by #335 when serving ri. PR #360 by Alex Wood. Don't try to parse svg files. Issue #350 by Sigurd Svela. Minor enhancements Improve class name expansion/resolution in ri. PR #400 by NARUSE, Yui Improve performance of document generation. PR #397 by Yusuke Endoh. 4.3.0 / 2016-11-04 Minor enhancements Removed json dependency for Ruby 2.4.0 End to support Ruby 1.8.x
2 participants
Addresses some concerns discovered and raised in #390.
Add coverage and resolve problem where versions don't show in just updated when there is only one.