-
-
Notifications
You must be signed in to change notification settings - Fork 347
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
✨ NeoDropdown & NeoSelect #4430
Conversation
✅ Deploy Preview for koda-nuxt ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
Awesome stuff! 😍 Is it mergeable already? |
J'ai hâte qu'il soit prêt pour que nous puissions l'utiliser 🥰 |
oh, I found it. need to add somehow if we didn't put the
|
I remember mentioning it in a comment, wanted to know if there was not a better approach like a general import. now my problem is that I can't override oruga variable on scoped element using |
i see, what hapeen if we try with sass variables? does the sass variable also get the same result? |
Sass variable ain't working :/ edit: might need some tweak
|
we need to reorder like this: @import '@oruga-ui/oruga/src/scss/utilities/expressions.scss';
@import '@oruga-ui/oruga/src/scss/utilities/variables.scss';
@import '@oruga-ui/oruga/src/scss/utilities/animations.scss';
@import '@oruga-ui/oruga/src/scss/utilities/helpers.scss';
$button-background-color: red !default;
$button-color: black !default;
// override another variables in here
@import '@oruga-ui/oruga/src/scss/components/button.scss';
// custom classes in here should work with scoped components. the order was:
wrong order will won't work as expected |
Code Climate has analyzed commit f279921 and detected 0 issues on this pull request. View more on Code Climate. |
Thanks for your help! I'm not really a fan of the current solution, but it look like it's working (don't work when using |
yes, would be happy if you found a cleaner solution. that's my approach in the past when I'm wrapping https://ant.design/ components |
what would be better solution? |
IMO there must be a better way to configure this stuff. otherwise we should really stop using oruga outside |
oh okay, for now we can merge then? |
I think it's good to go, don't mind failing test |
// TODO:
active
stylePR Type
Context
<NeoSelect />
component on histoire<NeoDropdown />
component on histoireBefore submitting pull request, please make sure:
Screenshot 📸