Slim Select 2.0!!! #356
Replies: 3 comments 2 replies
-
|
Hello! Is there any manual, to migrate from 1.27.1=>final version? I have a lot of issues vhile I try to change only js and css files(( |
Beta Was this translation helpful? Give feedback.
-
|
Sorry i dont. You shouldnt see anything crazy maybe some minor naming changes. I upgraded this to 2.0 so long ago i dont fully remember everything i changed. Check out the docs, everything you did previously should be pretty similar. |
Beta Was this translation helpful? Give feedback.
-
|
Where can i find documentation for 1.27.1? for making live search in modal. I need to make live search direct in sql for product. |
Beta Was this translation helpful? Give feedback.
-
|
I have issue with responce from server, it appending it to select, but it is invisible on page, and select stays blank and can not be selected
Получите Outlook для Android<https://aka.ms/AAb9ysg>
…________________________________
From: Brian Voelker ***@***.***>
Sent: Saturday, May 18, 2024 3:31:16 PM
To: brianvoe/slim-select ***@***.***>
Cc: polishchukI ***@***.***>; Comment ***@***.***>
Subject: Re: [brianvoe/slim-select] Slim Select 2.0!!! (Discussion #356)
Sorry i dont. You shouldnt see anything crazy maybe some minor naming changes. I upgraded this to 2.0 so long ago i dont fully remember everything i changed. Check out the docs, everything you did previously should be pretty similar.
—
Reply to this email directly, view it on GitHub<#356 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AOODQ7XL2RBKT75GW7GNL6LZC5CZJAVCNFSM6AAAAAASGA5RFSVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TINZYHE3TA>.
You are receiving this because you commented.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
pull an old tag. npm install, npm run dev, localhost:8080 |
Beta Was this translation helpful? Give feedback.
-
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!
This discussion was created from the release Slim Select 2.0!!!.
Beta Was this translation helpful? Give feedback.
All reactions