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
audit eslint / prettier configs - not catching uninitialized class members #116
Comments
task here would be to compare the eslint and prettier configs in both the example dir and the root dir with the ones from our cdk projects, such as: https://github.com/momentohq/cacheadmin-v2/tree/main/infrastructure/aws and And make sure nothing is terribly out of sync between them. Possibly also test the specific scenario described above and see if I am just misremembering or if there is an eslint setting that catches the case where you have an uninitialized readonly member var. |
@cprice404 This appears to be a typescript thing governed by We have turned it off everywhere but momentohq/serverless-api-demo/infra/aws/tsconfig.json. Turning it on in client-sdk-javascript reveals a couple issues.
@bruuuuuuuce @eaddingtonwhite Do you know why noUnusedLocals is off? |
okay. Thanks for looking into it @schwern . I think we can just put this on the backburner for now. |
Check and make sure that the eslint/prettier configs are up to date with what we've been using internally.
In particular - I noticed that if I was writing a class that had some private readonly member variables, and those variables were not initialized in the constructor, I didn't get a build/lint error. In our CDK repos I believe we would catch that at compile time.
The text was updated successfully, but these errors were encountered: