Bump slim-select from 1.27.1 to 2.6.0

[dependabot]

Bumps slim-select from 1.27.1 to 2.6.0.

Release notes

Sourced from slim-select's releases.

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!

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #1881.