Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[Test CI] Automatically comment on PRs that add `any` types
See original GitHub issueWe want the libdefs in this repository to remain high quality. As such, we want to minimize any types as much as is reasonably possible. In some cases an any type of some kind (including things like Object, Function, etc) is unavoidable – so we can’t simply ban them altogether.
To minimize the number of unnecessary any types, it would be good to have Travis check for these and comment on any pull requests that add them – pointing out that they should be avoided if at all possible.
Perhaps something like a --strict flag could be added to the validate-defs command that emits warnings on these kinds of things?
Issue Analytics
- State:
- Created 7 years ago
- Comments:8 (7 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I found [eslint-plugin-flowtype/no-weak-types]https://github.com/gajus/eslint-plugin-flowtype#eslint-plugin-flowtype-rules-no-weak-types and created a PR to this repo with config for that and will close my PR against eslint-plugin-flow-typed.
@jeffmo Looks like Hound CI has support for eslint and does inline comments of lint warnings. Might be an option?