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

feat: replace relative import closes #5484 #5487

Closed
wants to merge 37 commits into from

Conversation

umairraza96
Copy link
Contributor

@umairraza96 umairraza96 commented Jul 9, 2023

Description

Added a plugin for eslint eslint-plugin-no-relative-import-paths

Related Issues

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, and/or npx turbo test:snapshot to update snapshots if I created and/or updated React Components.
  • I've covered new added functionality with unit tests if necessary.

@umairraza96 umairraza96 requested a review from a team as a code owner July 9, 2023 12:13
@vercel
Copy link

vercel bot commented Jul 9, 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 Jul 12, 2023 10:03pm
nodejs-org-stories ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jul 12, 2023 10:03pm

@vercel vercel bot temporarily deployed to Preview – nodejs-org July 9, 2023 12:14 Inactive
@vercel vercel bot temporarily deployed to Preview – nodejs-org-stories July 9, 2023 12:14 Inactive
Copy link
Member

@mikeesto mikeesto left a comment

Choose a reason for hiding this comment

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

Thanks for the PR. I think this on the right track but these changes have broken storybook. Can you please have a look at this: https://github.com/nodejs/nodejs.org/actions/runs/5499772573/jobs/10027807119?pr=5487

@vercel vercel bot temporarily deployed to Preview – nodejs-org July 10, 2023 14:28 Inactive
@vercel vercel bot temporarily deployed to Preview – nodejs-org-stories July 10, 2023 14:29 Inactive
@umairraza96
Copy link
Contributor Author

Thanks for the PR. I think this on the right track but these changes have broken storybook. Can you please have a look at this: https://github.com/nodejs/nodejs.org/actions/runs/5499772573/jobs/10027807119?pr=5487

I have fixed the test issue but there is 1 snapshot test that is failing and I don't know whats causing it may be we need to record a new snapshot need assistance on this

@ovflowd
Copy link
Member

ovflowd commented Jul 10, 2023

Thanks for the PR. I think this on the right track but these changes have broken storybook. Can you please have a look at this: nodejs/nodejs.org/actions/runs/5499772573/jobs/10027807119?pr=5487

I have fixed the test issue but there is 1 snapshot test that is failing and I don't know whats causing it may be we need to record a new snapshot need assistance on this

Can you first rebase your branch? We did a few changes on some files that are conflicting.

Now, to update the snapshots you can simply run npm run test:storybook:snapshot

@vercel vercel bot temporarily deployed to Preview – nodejs-org-stories July 10, 2023 14:41 Inactive
@vercel vercel bot temporarily deployed to Preview – nodejs-org July 10, 2023 14:42 Inactive
@vercel vercel bot temporarily deployed to Preview – nodejs-org July 10, 2023 21:39 Inactive
@github-actions
Copy link
Contributor

github-actions bot commented Jul 10, 2023

📦 Next.js Bundle Analysis for nodejs.org

This analysis was generated by the Next.js Bundle Analysis action. 🤖

This PR introduced no changes to the JavaScript bundle! 🙌

@vercel vercel bot temporarily deployed to Preview – nodejs-org-stories July 10, 2023 21:39 Inactive
@vercel vercel bot temporarily deployed to Preview – nodejs-org-stories July 10, 2023 22:07 Inactive
@vercel vercel bot temporarily deployed to Preview – nodejs-org July 10, 2023 22:07 Inactive
@vercel vercel bot temporarily deployed to Preview – nodejs-org-stories July 10, 2023 22:31 Inactive
@vercel vercel bot temporarily deployed to Preview – nodejs-org July 10, 2023 22:32 Inactive
@vercel vercel bot temporarily deployed to Preview – nodejs-org-stories July 12, 2023 21:14 Inactive
@vercel vercel bot temporarily deployed to Preview – nodejs-org July 12, 2023 21:14 Inactive
@ovflowd
Copy link
Member

ovflowd commented Jul 12, 2023

FYI rebasing seems to be needed!

@vercel vercel bot temporarily deployed to Preview – nodejs-org-stories July 12, 2023 21:20 Inactive
@vercel vercel bot temporarily deployed to Preview – nodejs-org July 12, 2023 21:20 Inactive
@vercel vercel bot temporarily deployed to Preview – nodejs-org-stories July 12, 2023 21:58 Inactive
@vercel vercel bot temporarily deployed to Preview – nodejs-org July 12, 2023 21:59 Inactive
Used below command to revert back to the `build-and-analysis.yml` file
```bash
git checkout main -- .github/workflows/build-and-analysis.yml
```
@vercel vercel bot temporarily deployed to Preview – nodejs-org July 12, 2023 22:03 Inactive
@vercel vercel bot temporarily deployed to Preview – nodejs-org-stories July 12, 2023 22:03 Inactive
@ovflowd
Copy link
Member

ovflowd commented Jul 13, 2023

@umairraza96 could we do the rebasing or recreation once more? And then I'll prioritise getting this merged so that you don't need to worry about further rebases/updates! 🙇

@@ -46,7 +46,7 @@ jobs:
~/.npm
.next/cache
node_modules/.cache
key: cache-${{ hashFiles('package-lock.json') }}
Copy link
Member

Choose a reason for hiding this comment

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

Unrelated changes again over here :S

@@ -1 +1 @@
[]
Copy link
Member

Choose a reason for hiding this comment

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

Also unrelated changes here

Copy link
Member

Choose a reason for hiding this comment

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

Why we don’t put this file in gitinignore ?

Copy link
Member

Choose a reason for hiding this comment

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

This was already discussed before. And the file should not be on gitignore. (Also adding it right now would have 0 effects)

@umairraza96
Copy link
Contributor Author

umairraza96 commented Jul 13, 2023

@ovflowd I created a new branch #5513 which closes #5487

@ovflowd
Copy link
Member

ovflowd commented Jul 13, 2023

I see, you could simply have deleted this one, rebranch from main and force push, so that you wouldn’t need to create a new PR 🙈

But that’s okay, let’s close this one!

@mikeesto
Copy link
Member

Closing in favor of #5513

@mikeesto mikeesto closed this Jul 14, 2023
@umairraza96 umairraza96 deleted the feat/relative-imports branch July 21, 2023 16:01
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.

5 participants