-
Notifications
You must be signed in to change notification settings - Fork 6.2k
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
Adding NavItem #5973
Adding NavItem #5973
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
@ovflowd Bhaiya as instructed I opened a pull request for this issue . Even though I tried my level best to do it on first but failed by few hours 🙏 . I would be blessed if you accept my PR and it will be an honor for me to contribute in the codebase of NodeJS website |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good first contribution but some improvement can be done
@@ -0,0 +1,8 @@ | |||
<?xml version="1.0" encoding="UTF-8"?> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we accept idea IDE in this pr ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No. All these files should be deleted.
@@ -0,0 +1,39 @@ | |||
.navItem { | |||
@apply inline-flex items-center gap-2 rounded px-3 py-2; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Remember to reread the contribution guideline 😄
Example of how it's should write
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay Sir 😅
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can't imagine how your React Component is a 1:1 match of the other PR that was opened a few hours before yours.
It's impossible that you've made a 1:1 match of their PRs. I'm concluding that this violates our Contribution Guidelines and closing this PR.
If this is not the case, please feel free to justify your reasoning, and I apologize for any inconvenience. |
Sir to be honest I have created the components by my own with the help of JavaScript in a dummy folder since I lack knowledge of Typescript I referenced the PR and took code from it I am really very sorry for the same I hope you understand and forgive me 🙏🏻 |
Hey there. I understand that on your urge to make a contribution, and due to lack of knowledge you thought the best approach here was to go to another PR and copy their codebase. But that is never the solution. It's a non-ethical approach. Giving credits or not. Both of you want to make a meaningful contribution, and I (we) appreciate that, but there are ways of doing this without putting someone's effort in detriment. If you lack knowledge or are a novice, we're here to help. PRs can be opened as a draft, and you can always ask for support, guidance or instructions. There's nothing really to forgive as I doubt you had ill intents; But sadly I cannot allow this PR, hence it will not get merged. I hope you find this opportunity to find another issue soon (We're opening more issues soon) and be able to still contribute. I appreciate your energy and gesture, but keep in mind that this is not a competition about who merges first or et cetera; Have a good one! |
Description
Issue Solved : Create NavItem Component #5911
created NavItem component wtih help of typescript and tailwind css whole design is copied from the figma file provided by admin
Validation
Dark Mode
Light Mode
Also in the active stage the button gets converted in green color as specified in the figma file.
Related Issues
Create NavItem Component #5911
Check List
npx turbo lint
to ensure the code follows the style guide. And runnpx turbo lint:fix
to fix the style errors if necessary.npx turbo format
to ensure the code follows the style guide.npx turbo test
to check if all tests are passing.