fix: improve scanner accessibility and platform support - #31
Open
VincenzoImp wants to merge 1 commit into
Open
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
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.
Layer 4 (final) of the follow-up stack announced in #25, rebased onto the updated
devnow that #29 has landed.Summary
Note on
flutter_lintsThis layer also raises the
flutter_lintsdev dependency from^3.0.1to^6.0.0, with the correspondingpubspec.lockupdate. The stricter default rule set passes on the current tree, but it is a repo-wide change rather than an accessibility one — happy to split it into its own PR or drop it if you would rather keep this diff focused.Verification
flutter analyzecleandevreproduced the verified tree exactly, apart from the 1.3.0 release bump; one conflict inscanner_home_page.dartwas a hunk-alignment artifact and was resolved to the verified content