• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

marionettejs / backbone.marionette / 6393 / 1
100%
master: 100%

Build:
DEFAULT BRANCH: master
Ran 03 Oct 2017 05:46AM UTC
Files 43
Run time 2s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

03 Oct 2017 05:44AM UTC coverage: 100.0%. Remained the same
TEST_SUITE=coverage

push

travis-ci

web-flow
Use add at end perf only when sortWithCollection is false (#3471)

Because a collection can be modified without the full understanding on the collectionview, the optimistic adding that reduces perf is not ideal when `sortWithCollection: true`  This opens the door to all kinds of edge cases.  So we should only apply it when the collectionview itself is maintaining the sort.

However this brought up a related issue.  If a collection was `sortWithCollection: false` the _default_ `viewComparator` was still sorting with collection on add or update which mean that setting it to false only prevented a resort if `collection.sort()` was called directly, but not for any other circumstance.  If the collectionview is not maintaining the collection's sort, this prevents the sort from occurring at all.

853 of 884 branches covered (96.49%)

1718 of 1718 relevant lines covered (100.0%)

749.42 hits per line

Source Files on job 6393.1 (TEST_SUITE=coverage)
  • Tree
  • List 0
  • Changed 23
  • Source Changed 1
  • Coverage Changed 23
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Build 6393
  • Travis Job 6393.1
  • d9662096 on github
  • Prev Job for TEST_SUITE=coverage on master (#6391.1)
  • Next Job for TEST_SUITE=coverage on master (#6402.1)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc