Skip to content

Releases: cibernox/ember-power-select

Alphabet soup

25 Nov 19:37
Compare
Choose a tag to compare

It has been a loooong time since the last major release, but this one addresses one of the main problems with the component since its inception: A11y.

Thanks to the great contributions from the folks at Freshbooks in #1481, #1483 and #1484 this components is now nice to use for people using screen readers like VoiceOver or Jaws, properly announcing the selected and highlighted options.

The improvements required some changes in the aria attributes of the component which some people used for styling, hence why this could be considered a breaking change, although it will be simple upgrade for virtually everyone.

Home-made croissants

30 Apr 21:13
Compare
Choose a tag to compare

Finally a new major version!

When compared with 2.0.0-beta.5, it finally removes the dependency on ember-native-dom-helpers. Not the test helpers provided by this addon use the helpers in @ember/test-helpers.

When compared with the last 1.X version, I'll just copy the relevan breaking changes, which I don't expect they'll be relevant for most users:

Require Glimmer 2

Now the min version of Ember is 2.10. It allows the component to drop some code most people don't need anymore.
If you are not in Ember 2.10 or greater, don't worry. Branch 1.X will continue to support 2.3.1+ for some time while you upgrade.

Drop ember-wormhole

Now that we can rely on the glimmer-vm, the addon uses Ember-Basic-Dropdown 1.0, which uses the built-in #-in-element construct to render your content out of the regular flow of the page.

Better behaviour when typing on the trigger

Now when a select's trigger (not the searchbox) is focused and you type, the default behavior mimics much better the default behavior of native selects

Global acceptance helpers are deprecated.

The selectChoose, selectSearch, removeMultipleOption and clearSelected helpers will continue to exist, but registering and using them as globals is deprecated and will be removed on the 2.0 release. You can continue to use them just the same, but you will have to explicitly import them from ember-power-select/test-support/helpers. That is all!

Pulpo a feira

18 Dec 17:08
Compare
Choose a tag to compare
Pulpo a feira Pre-release
Pre-release

🎅 🎄 🎄 Ho Ho Ho! 🎄🎄 🎅

Santa came early with a new major version of Ember Power Select!
This kicks in the 2.0 series, the first one with (intentional) breaking changes in a long time. But fear not, you won't probably notice anything.

Require Glimmer 2

Now the min version of Ember is 2.10. It allows the component to drop some code most people don't need anymore.
If you are not in Ember 2.10 or greater, don't worry. Branch 1.X will continue to support 2.3.1+ for some time while you upgrade.

Drop ember-wormhole

Now that we can rely on the glimmer-vm, the addon uses Ember-Basic-Dropdown 1.0, which uses the built-in #-in-element construct to render your content out of the regular flow of the page.

Better behaviour when typing on the trigger

Now when a select's trigger (not the searchbox) is focused and you type, the default behavior mimics much better the default behavior of native selects

Global acceptance helpers are deprecated.

The selectChoose, selectSearch, removeMultipleOption and clearSelected helpers will continue to exist, but registering and using them as globals is deprecated and will be removed on the 2.0 release. You can continue to use them just the same, but you will have to explicitly import them from ember-power-select/test-support/helpers. That is all!

Wooper

13 Jul 15:06
Compare
Choose a tag to compare

Use new modules API.

So far, a banana

26 Apr 10:12
Compare
Choose a tag to compare

Now the select supports working inside elements with scroll!

Steak and salad

13 Apr 15:54
Compare
Choose a tag to compare

I head that summer is coming a it's time to start doing diet, right?

Well, Ember Power Select is doing that! 🎉
Starting with 1.7.0 the addon is 100% jQuery-free. You can the addon and the test helper that it provides on jQuery-free apps.

As a consequence of this CSS selectors passed to test helpers that end up in :eq() are now deprecated. They are still supported but will be removed in 1.8.0. Of you want to take the NTH option, now the selectChoose helper accepts a third numeric argument that can be used for the same thing you used to use :eq(number).

selectChoose('.language-picker', '.ember-power-select-option', 5); // It's going to select the 6th element that matches `.ember-power-select-option` query.

Fabada asturiana

13 Mar 15:31
Compare
Choose a tag to compare
Fabada asturiana Pre-release
Pre-release

This is the first version of the addon that is transpiled using Babel6 internally. It should still be usable even if your app still uses babel 5.

No new features since 1.5.0.

Yorkshire pudding

23 Jan 21:18
Compare
Choose a tag to compare

New minor version with a new and handy feature 🎉

Now you can pass a placeholderComponent to the select to have complex placeholders with HTML and logic. For those situation where a simple string is not enough.

screen shot 2017-01-23 at 21 17 24

Docs: http://www.ember-power-select.com/docs/the-trigger

Props to @montoias for the work!

Muesly (it's too early)

20 Jan 09:26
Compare
Choose a tag to compare

Thanks to the awesome work of @simonihmig , now the addon has LESS support on pair with SASS!
This also improved the blueprint to add the import statements without wiping the rest of the file.

Just a salad

12 Jan 12:20
Compare
Choose a tag to compare

First minor version bump in the 1.X cycle.

The main feature in this version is the usage of Ember.isEqual to compare options instead of a simple === operator.
Using this comparator function is unlikely to break anyone code, but I thought that it deserved a minor bump.

Among of the advantages of this are:

  • Better results when comparing dates. While in JS, new Date(2017, 5, 5) !== new Date(2017, 5, 5) because objects are compared by reference, this is hardly ever the intended behaviour. Ember.isEqual(new Date(2017, 5, 5), new Date(2017, 5, 5)) will correctly return true.
  • Allows the user to define their own way of comparing equality. If an object defines an isEqual(other) {} method it will be used instead of a simple ===. This allows users to decide that two POJOs should be considered equal if their id property is the same.