-
-
Notifications
You must be signed in to change notification settings - Fork 5.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
Add typescript guideline and typescript-specific eslint plugins and fix issues #31521
Conversation
I think we should try to run the TS eslint rules on JS before the migration because that will allow the migration to be pure renames. Not sure if that is really possible already but I will try. If the diff is to big, it will be in a separate PR. |
Ready for review again. |
@jolheiser odd, your review does not show up properly: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Second time's the charm?
Next and final step in the typescript journey: #31559 |
* giteaofficial/main: Fix slow patch checking with commits that add or remove many files (go-gitea#31548) Add typescript guideline and typescript-specific eslint plugins and fix issues (go-gitea#31521)
@typescript-eslint/eslint-plugin
, general typescript ruleseslint-plugin-deprecation
to detect deprecated code