Yauheni Prakopchyk
Yauheni Prakopchyk
Right now that has to be done manually. --- The complication of this issue stems from tricky testing. You also have add this as a parameter to release config.
**Vuestic-ui version:** 1.4.11
```ts export const getValueByKey = ( option: T, prop: string | ((option: T) => any), ): any => { // Can't access not object option if (typeof option !== 'object'...
Default scrollbar is not sexy enough. Maybe we can improve it a bit. * Ieally we want scrollbar to at least follow the theme (dark/light), so that it doesn't hurt...
**Vuestic-ui version:** 1.4.10 Probably best would be to check refs on that. Not sure what's the perfect approach.
## Why So far we had multiple issues with getting broken for new users. That's far from ideal as we don't have a visibility on the thing of most importance...
**Vuestic-ui version:** 1.4.11 - [x] Changing language gives error on mobile - [ ] We don't have a way to change language on docs (not landing). - [ ] Layout...
The idea is to have case.vue files, that contain both test and demo setups.
 Probably just needs a half-transparent white background for problematic images, but you can investigate a bit. Might be possible to do in context of markdown, github allowed some html...
Select needs an example with autocomplete. The case is where select has too much data (thousands), but we need to make it operable nonetheless. Pretty sure we can handle it...