Skip to content
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

Closed
wants to merge 1 commit into from
Closed

Adding NavItem #5973

wants to merge 1 commit into from

Conversation

DhairyaMajmudar
Copy link

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
image

Light Mode
image

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

  • I have read the Contributing Guidelines and made commit messages that follow the guideline.
  • I have run npx turbo lint to ensure the code follows the style guide. And run npx turbo lint:fix to fix the style errors if necessary.
  • I have run npx turbo format to ensure the code follows the style guide.
  • I have run npx turbo test to check if all tests are passing.
  • I've covered new added functionality with unit tests if necessary.

@DhairyaMajmudar DhairyaMajmudar requested a review from a team as a code owner October 7, 2023 14:22
@vercel
Copy link

vercel bot commented Oct 7, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
nodejs-org ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 7, 2023 2:23pm

@DhairyaMajmudar
Copy link
Author

DhairyaMajmudar commented Oct 7, 2023

@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

@AugustinMauroy AugustinMauroy added the github_actions:pull-request Trigger Pull Request Checks label Oct 8, 2023
@github-actions github-actions bot removed the github_actions:pull-request Trigger Pull Request Checks label Oct 8, 2023
@AugustinMauroy AugustinMauroy linked an issue Oct 8, 2023 that may be closed by this pull request
@github-actions
Copy link

github-actions bot commented Oct 8, 2023

Unit Test Coverage Report

Lines Statements Branches Functions
Coverage: 92%
90.95% (201/221) 72% (36/50) 87.75% (43/49)

Unit Test Report

Tests Skipped Failures Errors Time
17 0 💤 0 ❌ 0 🔥 4.189s ⏱️

Copy link
Contributor

@AugustinMauroy AugustinMauroy left a 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"?>
Copy link
Contributor

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 ?

Copy link
Member

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;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay Sir 😅

Copy link
Member

@ovflowd ovflowd left a 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.

@ovflowd ovflowd closed this Oct 8, 2023
@ovflowd
Copy link
Member

ovflowd commented Oct 8, 2023

If this is not the case, please feel free to justify your reasoning, and I apologize for any inconvenience.

@DhairyaMajmudar
Copy link
Author

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 🙏🏻

@ovflowd
Copy link
Member

ovflowd commented Oct 8, 2023

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Create NavItem Component
3 participants