Skip to content
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

Potential Bug Risks and Anti-Patterns #172

Closed
HarshCasper opened this issue Dec 21, 2020 · 1 comment
Closed

Potential Bug Risks and Anti-Patterns #172

HarshCasper opened this issue Dec 21, 2020 · 1 comment

Comments

@HarshCasper
Copy link

Description

I ran DeepSource Static Code Analysis upon the Project, the results for which are available here.

The Static Code Analysis Tool found potential bugs and anti-patterns in the Code, that can be detrimental at a later point of time with respect to the Project. DeepSource helps you to automatically find and fix issues in your code during code reviews. This tool looks for anti-patterns, bug risks, performance problems, and raises issues.

Some of the notable issues are:

  • Instances of child_process and non-literal exec() here
  • Use of require statements except in import statements here
  • rest parameters used instead of arguments here
  • Using String Concatenation instead of template literals here

There are plenty of other issues in relation to Bug Discovery and Anti-Patterns which you would be interested to take a look at.

@gempain
Copy link
Contributor

gempain commented Dec 21, 2020

@HarshCasper thanks for opening and issue and reporting this. I looked through the reports and reviewed the warnings. Most of them belong to development helpers or test files. For those in the core code, none of them represents something we should be worried about.

@gempain gempain closed this as completed Dec 21, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants