Change ViewModel visibility from public to internal for all feature modules #1924
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.
What I have done and why
Changed the visibility modifier of all ViewModel classes within their respective feature modules from public to internal, ensuring that ViewModels are only accessible within their own modules.
This modification improves encapsulation and enforces clear module boundaries, preventing unintended usage of ViewModels across modules.
By restricting access with the internal modifier, the codebase becomes more maintainable and less prone to unintended dependencies.
Updated each feature module separately to reflect this visibility change, keeping each commit modular and easier to review.
Updated Modules
The following feature modules have been updated: