issue(42): Unable to Mock FlutterEasyDialogs in Unit Tests #43
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
feduke-nukem
approved these changes
Nov 26, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Status
READY
Breaking Changes
NO
Description
Removed
@visibleForTestingannotation fromFlutterEasyDialogs.controllergetter to make it part of the public API.Previously, the
controllergetter was marked as visible only for testing purposes. This limitation prevented developers from working with the controller directly and made it impossible to mock the controller in tests without accessing the internal singleton throughFlutterEasyDialogs.Changes:
@visibleForTestingannotation fromFlutterEasyDialogs.controllerCHANGELOG.mdwith feature descriptionResolves #42
Type of Change