This repository has been archived by the owner on Dec 19, 2022. It is now read-only.
Some code fixes based on alerts from lgtm.com #21
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Explanation About What Code Achieves:
Bottery is being analysed by lgtm.com: https://lgtm.com/projects/g/google/bottery/. This PR fixes four alerts (in separate commits) flagged up by lgtm.com. I hope it's of use!
Steps To Test:
The changes shouldn't change any of the behaviour of the code, exception for my change in
js/io.js
. However, the code that I changed does not seem to be used.TODOs:
If you think these fixes are useful and would like to make sure problems like these are not accidentally introduced in the future: consider enabling automatic code reviews through PR integration on https://lgtm.com/projects/g/google/bottery/ci/
Here's an example of how NASA are using automatic code reviews for their Open-MBEE project: Open-MBEE/exec-cameo-mdk#105
(full disclosure: I'm part of the team behind lgtm.com 😄 — let me know if you have any feedback!)