Refactoring for code convention

[ancy0]

Describe changes

Refactor the entire code according to the rules defined by the meeting

Issue number or link

Types of changes

What is the type of code change?
Put an x in the boxes that apply

• Bugfix (changes that resolve errors)
• New feature (changes which adds functionality)
• Breaking change (big changes that affect existing functionality)
• Documentation Update

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• I have read the "README.md"
• My code follows the style guidelines of this project
• My changes generate no new warnings
• Lint and unit tests pass locally with my changes
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation
• Any dependent changes have been merged and published in downstream modules

Further comments

Please let me know if there's anything else to explain

[sinji2102]

Good Refactoring 😄

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[hummingbbird]

💯