v2.9.0

What's Changed

• Make CSS classes overridable during initialization by @Data5tream in #530
• Fix Home page navigation to Vue example by @Ovi in #531
• Adding focus search option by @andy-UKC in #529
• Unit tests by @Data5tream in #535
• Text Highlighter Update by @Tonksthebear in #545
• Bubble change event up to other element by @frenkel in #547
• Allow key presses not relevant to SlimSelect to propagate to default handlers by @meagar in #550
• Update paths to type declaration files in package.json by @Miodec in #559
• Select options by id by @deh-code in #555

New Contributors

• @Data5tream made their first contribution in #530
• @Ovi made their first contribution in #531
• @Tonksthebear made their first contribution in #545
• @frenkel made their first contribution in #547
• @meagar made their first contribution in #550
• @Miodec made their first contribution in #559
• @deh-code made their first contribution in #555

Full Changelog: v2.8.2...v2.9.0

v2.7.0

A bunch of various tasks.

• package updates
• react integration
• destroy event listener bind update
• highlight update to start on selected
• added docs for setSelected second param
• removed conflicting id
• store addition of getting first option
• custom focus color
• a few older others

v2.0.2

Fixed build output. See https://slimselectjs.com/install#cdn

Slim Select 2.0!!!

Version 2 release today!

The biggest part of this release was completely restructuring communication between javascript classes. The structure now is based upon responsibility. So the main index will communicate with the store, original select and rendering as it sees fit. If the original select changes, it will communicate that back to the main index and based upon that callback will choose what to do with that information. Same goes for the render for searching and option selection.

The next decent change is the separation of settings from events into sub objects. This makes it easier for a couple of different reasons. 1. Reusing certain settings but having different change callbacks. 2. Next step is I am going to release a vue version and passing props is easier as an object of fields appose to individual fields. I would assume that to be the case for react as well, which I do plan on releasing(might need some help from the community). This does require migration of old code into the correct sub object of settings.

With the settings and events separation some of the settings fields and event callback functions may have some slightly different names or return values. This was to help clean things up. You shouldn't have any missing features from v1 they may just be handled slightly differently.

With that being said the last change was with getting rid of ajax. Well sort of. Slim Select 2 now deals with these ajax/fetch based events as promise returns in the search event. See docs for more detail.

Slim select was fully built with typescript. This helped tremendously for finding issues not easily catch able without typescript declarations. the dist output has all the declarations for slim select in it.

Hopefully this gets everyone back on track with this project and if there is anything that needs address please file an issue and if you can please try to create a pr for it. Hopefully its easier to follow and understand now. Thanks!