You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think that, perhaps, the only difference between them ought to really just be how we handle events.
KRouterLink takes a :to route which must be a valid router route.
KExternalLink takes a download prop (among others) to manage external URL links
KButton goes "click" if you click it and you can do what you want with that information.
All of them should have:
Primary or no?
Appearance basic-linkraised-buttonflat-button
icon and iconAfter props & slots w/ a consistent sizing/styling
disabled prop
And I'm suggesting that If any of the components receive the same values for these props, they should look 100% identical. The only difference being how they act.
The text was updated successfully, but these errors were encountered:
- Cannot use KRouterLink because it targets internally
- Want KRouterLink styles here, though, and I've had to hack
that together with margins and my eyeballs
- KDS issue: learningequality/kolibri-design-system#82
will track this in an upcoming release.
I think that, perhaps, the only difference between them ought to really just be how we handle events.
:to
route which must be a valid router route.download
prop (among others) to manage external URL linksAll of them should have:
basic-link
raised-button
flat-button
icon
andiconAfter
props & slots w/ a consistent sizing/stylingdisabled
propAnd I'm suggesting that If any of the components receive the same values for these props, they should look 100% identical. The only difference being how they act.
The text was updated successfully, but these errors were encountered: