🐛 Bug Fix

• #77 Update forked package links (@RobbieTheWagner)

Committers: 1

• Robbie Wagner (@RobbieTheWagner)

💥 Breaking Change

• #75 Ember >= 3.24, node >= 14 (@rwwagner90)
• #72 Update liquid-fire, remove getowner polyfill (@rwwagner90)
• #67 ci: drop support for node 4.x and node 6.x (@alexdiliberto)

🚀 Enhancement

• #74 Add Embroider support (@rwwagner90)
• #73 Various Ember updates (@rwwagner90)

Committers: 2

• Alex DiLiberto (@alexdiliberto)
• Robert Wagner (@rwwagner90)

• Various bugfixes, minor CSS changes, etc
• Yields the parameters provided by components when using send, allowing the user to use what the component yielded in the block form liquid-wormhole

See the new documentation for new features and deprecations

Liquid Wormhole v2

Breaking Changes:

• The to property is no longer required when using liquid-wormhole. By default, new wormholes will now always show and not replace each other. If you want to have the old replacement logic, you can use the stack property to specify which stack the wormholes belong to, and which they should replace.
• Using explode for transitions is no longer necessary. You can use standard liquid-fire transitions as if you were animating any other element.
• The target helper is no longer necessary. You can use standard liquid-fire matchers instead:

{{liquid-wormhole class="modal"}}

this.transition(
  this.hasClass('modal')
);

• The onOpenWormhole and onCloseWormhole helpers are no longer necessary. When a wormhole is transitioning to an empty state, the toValue will be null. You can do something like this to replace onOpenWormhole:

this.transition(
  this.toValue(true)
);

• Because the toValue and fromValue may now be null, you may have to guard your matching statements.