@webitel/ui-sdk 24.2.42 → 24.2.43
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/ui-sdk.css +1 -1
- package/dist/ui-sdk.mjs +4 -4
- package/dist/ui-sdk.umd.js +2 -2
- package/package.json +1 -1
- package/src/components/wt-select/wt-select.vue +18 -2
package/package.json
CHANGED
|
@@ -196,9 +196,25 @@ export default {
|
|
|
196
196
|
},
|
|
197
197
|
methods: {
|
|
198
198
|
// for taggableMixin functionality
|
|
199
|
-
handleCustomValue(toggle) {
|
|
200
|
-
|
|
199
|
+
async handleCustomValue(toggle) {
|
|
200
|
+
/**
|
|
201
|
+
* tag emits input event, but there is a drawback
|
|
202
|
+
* there are causes, when input handler is async, but close event, emitted by toggle(),
|
|
203
|
+
* is performing some operations with input value.
|
|
204
|
+
* filter selects (abstract-enum(api)-filter.vue) for instance
|
|
205
|
+
*
|
|
206
|
+
* for now, i've tested this cause and it works well even without waiting for $nextTick()
|
|
207
|
+
* however, this is a potential problem, so, i've left this comment here
|
|
208
|
+
*/
|
|
201
209
|
this.tag(this.searchParams.search);
|
|
210
|
+
// await this.$nextTick();
|
|
211
|
+
|
|
212
|
+
/**
|
|
213
|
+
* call toggle strictly after tag() method because tag() emits input,
|
|
214
|
+
* because there could be code, which performs operation with input only after select close
|
|
215
|
+
* so that, it's crucial to emit input before close
|
|
216
|
+
*/
|
|
217
|
+
toggle();
|
|
202
218
|
},
|
|
203
219
|
// for taggableMixin functionality
|
|
204
220
|
emitTagEvent(searchQuery, id) {
|