-
-
Notifications
You must be signed in to change notification settings - Fork 4.7k
added new component Dropdown #2944
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
Conversation
Codecov Report
@@ Coverage Diff @@
## next #2944 +/- ##
==========================================
- Coverage 88.20% 85.37% -2.84%
==========================================
Files 50 57 +7
Lines 1009 1121 +112
Branches 399 441 +42
==========================================
+ Hits 890 957 +67
- Misses 76 105 +29
- Partials 43 59 +16
Continue to review full report at Codecov.
|
|
@flyingcircle, I have upgraded it. |
|
Very nice! Yes, this is more like what I was thinking. I'm wondering though, it looks like you copied a good chunk of the code over. Why just use |
|
I have a doubt, it is not called |
|
@flyingcircle yes, there is a reason, I was thinking as it would add more flexibility and rigidity. As further updated or modification to |
|
@arpitBhalla |
|
@flyingcircle what's your opinion, should it need to be changed to |
|
Decided to go with #2953 as it fit in a bit more with existing code. |
What kind of change does this PR introduce?
This PR will introduces a new component Dropdown to RNE.
Did you add tests for your changes?
Yes all changes are tested.
If relevant, did you update the documentation?
Yes Documents have been updated
Summary
There will be new component to Dropdown to RNE which was long awaited request, and need not to be installed from other npm packages separately. Also this dropdown can be act as Accordion https://media.geeksforgeeks.org/wp-content/uploads/20190522140003/accordian.gif
Does this PR introduce a breaking change?
No