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

Fix Sonarqube reported Code Smells #548

Closed
daltonfury42 opened this issue Feb 20, 2021 · 10 comments
Closed

Fix Sonarqube reported Code Smells #548

daltonfury42 opened this issue Feb 20, 2021 · 10 comments
Labels
good first issue Good for newcomers You Can Do This Will be accepted on priority

Comments

@daltonfury42
Copy link
Collaborator

We have accumulated some easy to fix security vulnerabilities over the last few months over here.

These are straightforward easy fixes, good for a new comer to take up as a good first issue.

Once they are fixed, we should see if a branch protection rule can be set to catch them pre-merge

@daltonfury42 daltonfury42 added good first issue Good for newcomers You Can Do This Will be accepted on priority labels Feb 20, 2021
@hallelshohat
Copy link
Contributor

I've made a pull request solving this issue

@daltonfury42
Copy link
Collaborator Author

daltonfury42 commented Feb 27, 2021

Thanks @hallelshohat for fixing the security hotspots. Now what is left is some code smells here that if anyone is interested, can go through and fix.

@daltonfury42 daltonfury42 changed the title Fix Sonarqube reported security vulnerabilities Fix Sonarqube reported Code Smells Mar 6, 2021
@daltonfury42
Copy link
Collaborator Author

I have gone through the list of issues and resolved a few as false positive after our discussions on #564

@maaverik @mradenovic If you get time, go through the codesmells and let me know if we need there are any more such false positives

@skShekhar
Copy link
Contributor

@daltonfury42 Are there anymore code smells or can this issue be closed?

@maaverik
Copy link
Collaborator

Hey @skShekhar. Sorry, missed your comment here. There are still a few small issues left, like the many TODOs we have. Let's leave this open so that we at least have a tracker that we can look at.

@mog-rn
Copy link
Contributor

mog-rn commented Aug 7, 2021

Hey @daltonfury42 I'm new to open source and I wanted to tackle this issue.
I was hoping you could give me a heads up on how I could tackle this one.

@daltonfury42
Copy link
Collaborator Author

@mog-rn
Copy link
Contributor

mog-rn commented Aug 7, 2021

ok thanks for the heads up @daltonfury42. I'll get back when i'm done

@divyansh21jain
Copy link

Hello @MogakaMo I just saw the list of issues described in the list and would be happy to contribute.

@maaverik
Copy link
Collaborator

maaverik commented Sep 9, 2021

Closing this since it looks like this is all covered.

@maaverik maaverik closed this as completed Sep 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers You Can Do This Will be accepted on priority
Projects
None yet
Development

No branches or pull requests

6 participants