chore: exclude non-business logic from coverage #10
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.



This pull request updates the
sonar-project.propertiesfile to refine the coverage exclusions for SonarQube analysis, ensuring that specific generated and model-related files are excluded from coverage metrics.The rationale for these exclusions:
/model//.kt: These are data classes and models that only contain properties and basic serialization. They don't contain business logic that needs testing.
/generated//: Generated code should not be included in coverage metrics as it's automatically generated and maintained.
**/Binding.kt, **/BindingImpl.kt: DataBinding related files that are generated by the Android framework.
**/_Factory.kt, **/_MembersInjector.kt: Dependency injection related generated files.
Updates to SonarQube configuration:
sonar-project.properties: Expandedsonar.coverage.exclusionsto include additional file patterns for exclusion, such as**/model/**/*.kt,**/generated/**/*, and several specific file suffixes like*Binding.kt,*BindingImpl.kt,*_Factory.kt, and*_MembersInjector.kt. This helps to exclude non-essential or auto-generated files from coverage analysis.