-
-
Notifications
You must be signed in to change notification settings - Fork 102
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
[FEATURE] Resolve the existing Next.js lint issues #328
Comments
Hi @ashmit-coder, I would like to contribute in this issue. I'm new to open source and I think I would like to give it a try. |
Sure go ahead 😊 |
hi @ashmit-coder , i would like to contribute . |
Hey @95481 sorry but @kavania2002 is working on it if he/she is unable to complete it you can pick up the task |
Hey @ashmit-coder, I have updated the code accordingly. Please have a look into it. |
Why do we need this improvement?
To improve the lint flow of the website and put proper checks in place.
NOTE
: This is a breaking change hence, when you work on this make sure to not dirupt the functionalityHow will this change help?
It will make better use of Next.js components and hence improve in website performance.
Screenshots
How could it be implemented/designed?
npm run lint
command.🚧 Breaking changes
Yes
👀 Have you checked for similar open issues?
🏢 Have you read the Contributing Guidelines?
Are you willing to work on this issue?
No, someone else can work on it.
Suppoerted issues
#306
Supported PR
#307
The text was updated successfully, but these errors were encountered: