migrate to null-safety codes and Flutter 3.3.0 #22
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
|
Thanks for the PR, |
…non-xml attr & tags part
Signed-off-by: lijun zhou <[email protected]>
support widgetEnumMap in valueTransformers
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hi Waseemdev,
Would like to update you that we have updated this extension to generate null-safety codes and having running our apps with Flutter 3.3.0 for weeks. Here I'm creating the pull request to merge back changes. Similarly we have updated the flutter_xmllayout_helpers lib to null-safety and Flutter 3.3.0
Thanks,
-James