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
[Tabs] Add a TabIndicatorProps property #11254
[Tabs] Add a TabIndicatorProps property #11254
Conversation
@adeelibr Thanks for giving a shot at this issue :). I think that there is a misunderstanding. The feature you want to introduce in this pull-request was removed in #10999. |
@oliviertassinari Oh okay that makes sense, my bad! let me make some changes to my PR. |
I have added a new prop in the Examples of using it
|
5efa82a
to
4a42ebf
Compare
4a42ebf
to
587893d
Compare
@adeelibr It's a great first pull request on Material-UI 👌🏻. Thank you for giving it a shot! |
@oliviertassinari I am super excited, this was my first open source PR. Thank you for helping me out with this PR. I intend to be more active in open source. Is there a possibility that if I stay active in contributing here that I can become an official member of the team? (Although I know I am new at this, but the experience has just been awesome, The learning and growth working is huge) Is there a road map for this, also can I work in improving docs in material ui as well? I mean I can start working on that as well. |
I reviewed the changes that you made to the PR, can you be so kind enough to tell me how is that you are passing Also how is it that you are using type script in material ui? Can you share some resources please so that I can study on it, that way I can contribute better next time. Thank you. |
Also I tried updating my local forked branch to get it synced with the latest material-ui with the following commands
This gives me an error
|
This project works through meritocracy. The more value one contributor brings to the project, the more responsibilities he gets. Yes, people who joined the core team have been people undertaking important improvements, people deeply caring about the future of the project, people sharing the same vision for the project. There is no fixed roadmap. There are the opened issues. There is the closed issue history. There are issues that bring context. There are the problems you face in the production projects you are working on. There are the documentation vision, api, roadmap, governance etc. There are milestones where we try to share a sense of what's important. But more importantly, contributing to open source test people resilience. Most people gives up. You won't learn from "me", you will learn from others. |
this is an initial commit change, I have just added a prop validation so that indicator color can accept a string also with secondary and primary.
Closes #11085