-
Notifications
You must be signed in to change notification settings - Fork 4
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
warning Missing return type on function #3
Comments
Nvm just pulled your latest update that fixed this! 95ac64a |
@BlueAccords The error still exists in the test file, and I am still trying to get that to work. Having a discussion here: typescript-eslint/typescript-eslint#384 |
Oh ok, i'll keep an eye out for updates to the repo then. Do you think it'll cause any problems if I use your boilerplate as a base for development or will I run into issues if I try to write tests due to the same issue? |
I will update this repo as soon as I get a response from someone there. Also, I am trying to convert this into a npm package so that you don't have to copy paste it and can just use npm versions to update the whole boilerplate. |
The issue still has a workaround that you explicitly mention void as a return type on test functions, which can be a short term solution. Apart from that, I don't think it would break anything else. |
Alright. Also with the latest version i'm getting this error when trying to run tests but i'm assuming this is the same one you're running into and trying to resolve .
|
@BlueAccords I updated the project, Could you take the latest change, remove the node modules and do a fresh install? |
Alright quick run through on a fresh pull, |
Is what I get after running
npm install
andnpm run dev
on the project.Didn't make any changes to the default files.
App.tsx
isIs the
explicit-function-return-type
typescript rule just too strict and not recommended to have on or am I missing something?The text was updated successfully, but these errors were encountered: