[wip] null-safety for android_alarm_manager_plus #51
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
- Removed discontinoued dependencies - plugin is null safe - example and e2e tests are yet not null safe as the integration_test package does not support null safety yet.
|
Null safety needs to be enabled on CI |
miquelbeltran
changed the title
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
Description
android_alarm_manager_plusis null safeintegration_testpackage does not support null safety yet.0.5.0to0.6.0-nullsafety.0Related Issues
#50
Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?