-
Notifications
You must be signed in to change notification settings - Fork 1
chore: fix errors #16
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
Conversation
| }), | ||
| }, | ||
| ); | ||
| // eslint-disable-next-line @typescript-eslint/no-explicit-any |
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.
need to fix at some point
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.
yeah there needs to be a real type for it, i'll try to see if there's a type for it in d.js or @d.js/rest
|
|
||
| app.get("/", async (_req, res) => { | ||
| // TODO: handle error | ||
| // eslint-disable-next-line @typescript-eslint/no-unused-vars |
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.
need to fix at some point
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.
could maybe return 500 if it errors? but then we would need an error page...
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.
i'll handle the error page stuff 👍
GalvinPython
left a comment
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.
thanks for fixing the eslint issues. Don't want to have the ignore comments, but that's for another time
another self explanatory pr, just fixes most of the typescript and eslint errors
some of them I had to
// eslint-disable-next-linebecause there's no other fix for it