-
Notifications
You must be signed in to change notification settings - Fork 27.6k
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
Detect typos for GS(S)P #20527
Comments
I misspell |
I think this feature would be very helpful. Since Next.js 11 now supports ESLint out of the box, I opened PR to add no-typo rule to Next.js's eslint |
This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you. |
Feature request
Is your feature request related to a problem? Please describe.
We should intelligently detect common typos in page exports for
getStaticProps
/getServerSideProps
/et al.Describe the solution you'd like
If a user exports
getServurSideProps
, we should throw an error and ask them if they've made a typo.Describe alternatives you've considered
Throw no error.
Additional context
Since these method's names are critical to code elimination, we should try to catch typos for optimal DX.
The text was updated successfully, but these errors were encountered: