Yauheni Prakopchyk

Results 233 issues of Yauheni Prakopchyk

I don's see a particular need to switch to storybook (there are upsides, but there are also downsides). I.e. storybook is very close to what we have in docs (and...

ready for implementation
test

![image](https://user-images.githubusercontent.com/5394573/182212682-20212282-65f3-4cad-ab69-dabec1783aa8.png) - [ ] speaking of `href(unknown) target to`, `active-class`, `exact-active-class` - [ ] Bonus points for checking other components for similar weirdness

BUG
good first issue
LOW PRIORITY
accessibility

Check if we can integrate existing services into ag-grid. Speaking of - [ ] CSS variables - [ ] Colors - [ ] Config Basically, everything we could integrate -...

FEATURE
ready for implementation

We want vuestic to be great. For that - it has to cover most users needs. Ideally do almost everything other solutions on the market do already. Right now we...

HIGH PRIORITY
research
ready for research

All of our competitors have some sort of navigation on the page and I can see a lot of value from it going forward. ![image](https://user-images.githubusercontent.com/5394573/179704130-df86f6f6-78a8-4c8a-ba69-517b21a440dd.png) - [ ] Implement right...

docs
design
difficulty 2: easy
value 2: nice to have

The idea is to apply filters to selection. I.e., let's assume you filter the tree, then you select a parent. Only filtered items should be selected (event if parent has...

FEATURE
component
difficulty 4: hard
value 3: wish to have

If page is not present - we redirect to `/`. That's not correct. We should have 404 instead. - [ ] Needs design. @xx13 that's not for current release.

docs
HIGH PRIORITY
ready for design

We decided to have 1st class tailwind support, so we'd scrape some of our helpers, and just link tailwind solutions instead. That's not an easy process so let's think it...

planning

Updating docs is a bit problematic. As you can have update happen when user has page loaded. If they try to navigate to some page - they might have an...

docs
LOW PRIORITY

Currently `hoveredOption` is used to represent both mouse hover and keyboard navigation. This is not ideal. - [ ] add `selectedOption` to track keyboard navigation. - [ ] use `hoveredOption`...

BUG
good first issue
ready for implementation
difficulty: hey not too rough