-
Notifications
You must be signed in to change notification settings - Fork 11
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 sonar issues and smells #97
Labels
Comments
sf-sahil-jassal
added a commit
that referenced
this issue
Jan 9, 2024
fix sonar code smells related to promises, and any types GH-97
sf-sahil-jassal
added a commit
that referenced
this issue
Jan 9, 2024
attempt to fix sonar code smell related to duplicate blocks of code by refactoring the chunks of code GH-97
12 tasks
sf-sahil-jassal
added a commit
that referenced
this issue
Jan 9, 2024
fix sonar code smells after new analysis related to camel case conventions of mixins, any types and unexpected console statements GH-97
sf-sahil-jassal
added a commit
that referenced
this issue
Jan 9, 2024
reduce sonar cloud duplications by refactoring the repeated lines of code in audit mixin GH-97
sf-sahil-jassal
added a commit
that referenced
this issue
Jan 9, 2024
reduce sonar cloud duplications by refactoring the repeated lines of code in audit mixin GH-97
yeshamavani
pushed a commit
that referenced
this issue
Jan 10, 2024
* refactor(chore): fix sonar code smells fix sonar code smells after new analysis related to camel case conventions of mixins, any types and unexpected console statements GH-97 * refactor(chore): reduce sonar duplicate lines of code reduce sonar cloud duplications by refactoring the repeated lines of code in audit mixin GH-97
🎉 This issue has been resolved in version 5.3.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Fix sonar issues and smells
https://sonarcloud.io/summary/overall?id=sourcefuse_loopback4-audit-log
The text was updated successfully, but these errors were encountered: