refactor: simplify singleton and improve NetworkInfo documentation #3726
+47
−27
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.
Pull Request Description
Overview
This pull request refactors the NetworkInfo singleton implementation and improves the overall code clarity and documentation. No functional or behavioral changes are introduced.
Details
Refactored the singleton pattern to a clearer and safer implementation
Improved inline documentation for better readability and maintainability
Clarified platform-specific behavior and limitations
Preserved the existing public API to ensure full backward compatibility
Impact
No breaking changes
No runtime behavior changes
No API modifications
Testing
No additional tests were required as this change does not affect runtime logic or functionality.
Checklist
Public API remains unchanged
No breaking changes introduced
Code formatted according to Dart style guidelines
Documentation reviewed and updated
Description
Related Issues
Checklist
CHANGELOG.mdnor the plugin version inpubspec.yamlfiles.flutter analyze) does not report any problems on my PR.Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?
!in the title as explained in Conventional Commits).