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(linter): implement @next/next/no-document-import-in-page #1997

Merged
merged 3 commits into from
Jan 13, 2024

Conversation

kaykdm
Copy link
Contributor

@kaykdm kaykdm commented Jan 11, 2024

@github-actions github-actions bot added the A-linter Area - Linter label Jan 11, 2024
@kaykdm kaykdm force-pushed the no-document-import-in-page branch from b7722b2 to 21db74b Compare January 11, 2024 13:10
Copy link

codspeed-hq bot commented Jan 11, 2024

CodSpeed Performance Report

Merging #1997 will not alter performance

Comparing kaykdm:no-document-import-in-page (3a905e1) with main (c70a065)

Summary

✅ 14 untouched benchmarks

@kaykdm kaykdm force-pushed the no-document-import-in-page branch from 21db74b to 7bbd3ac Compare January 11, 2024 13:23
@kaykdm kaykdm marked this pull request as ready for review January 11, 2024 13:28
@kaykdm kaykdm force-pushed the no-document-import-in-page branch from a26fd1d to e1f355a Compare January 12, 2024 12:44
Copy link
Contributor

@camc314 camc314 left a comment

Choose a reason for hiding this comment

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

Thank you!

@camc314 camc314 enabled auto-merge (squash) January 13, 2024 17:36
@camc314 camc314 force-pushed the no-document-import-in-page branch from 87924e2 to 921438a Compare January 13, 2024 17:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-linter Area - Linter
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants