Skip to content

Releases: html-next/vertical-collection

Release 3.1.0

04 Aug 09:37

Choose a tag to compare

🚀 Enhancement

🐛 Bug Fix

Committers: 3

Release 3.0.0

03 May 15:34

Choose a tag to compare

v3.0.0

Release 3.0.0

Release 3.0.0-1

01 Mar 14:04

Choose a tag to compare

Release 3.0.0-1 Pre-release
Pre-release
v3.0.0-1

Release 3.0.0-1

Release 3.0.0-0

09 Dec 22:37

Choose a tag to compare

Release 3.0.0-0 Pre-release
Pre-release

What's new

  • Drop support for Ember < 2.18, add support for Ember 4.0+ (#343) (3343ecc)
  • 4 retries on CI, 1s sleep (#352) (4a75d99)
  • Extend timeout for base tests, tweak retry (#351) (8fff4c7)
  • Remove implicit this in tests (#349) (5f58de6)

Release 2.1.0

09 Dec 03:12

Choose a tag to compare

Changelog:

  • Upgrade ember-cli and dev deps (#348) (e8924e9)
  • Drop Ember global use in favor of native API (#347) (d101d8a)
  • Proper runloop imports (#346) (a765241)
  • Remove property fallback lookup (no implicit this) (#345) (506d798)
  • Modernize htmlSafe module imports / More cleanup (#344) (32e9460)
  • Update CI for vertical-collection v2 (#342) (5613faa)

Release 2.0.1

07 Dec 14:06

Choose a tag to compare

🐛 Bug Fix

🏠 Internal

Committers: 2

v2.0.0

11 Feb 15:10

Choose a tag to compare

v1.0.0-beta.14...v2.0.0

v2.0.0-0

10 Feb 20:53

Choose a tag to compare

v2.0.0-0 Pre-release
Pre-release

v1.0.0-beta.14...v2.0.0-0

v1.0.0-beta.9

16 Nov 18:35

Choose a tag to compare

v1.0.0-beta.9 Pre-release
Pre-release

This release contains a few breaking changes in vertical-collections behavior:

  • The vertical-collection component is now tagless by default. This means it can be used directly in your templates just about anywhere, and it won't affect your existing styles at all. If you were previously using tagName to change the element of the collection this will still work and add a tag, but that element will by default become the scroll container for the collection. You must use containerSelector to change it to a different parent if you want to.
  • The collection now creates and removes elements from the pool of rendered components dynamically based on actual component size and container size. This means that it will automatically check after each render to see if more components need to be rendered (incremental rerender), and remove components if too many were rendered. Users shouldn't notice a difference in day-to-day usage, but it could affect tests they expected certain items to exist at a given time.

This is expected to be the final beta before we release v1.0.0 🎉