[various] Use RadioGroup for groupValue and onChanged
Use RadioGroup to avoid deprecated groupValue and onChanged (flutter/flutter#170915)
Pre-Review Checklist
- [X] I read the Contributor Guide and followed the process outlined there for submitting PRs.
- [X] I read the Tree Hygiene page, which explains my responsibilities.
- [X] I read and followed the relevant style guides and ran the auto-formatter.
- [X] I signed the CLA.
- [X] The title of the PR starts with the name of the package surrounded by square brackets, e.g.
[shared_preferences] - [X] I linked to at least one issue that this PR fixes in the description above.
- [X] I updated
pubspec.yamlwith an appropriate new version according to the pub versioning philosophy, or I have commented below to indicate which version change exemption this PR falls under[^1]. - [X] I updated
CHANGELOG.mdto add a description of the change, following repository CHANGELOG style, or I have commented below to indicate which CHANGELOG exemption this PR falls under[^1]. - [X] I updated/added any relevant documentation (doc comments with
///). - [ ] I added new tests to check the change I am making, or I have commented below to indicate which test exemption this PR falls under[^1].
- [X] All existing and new tests are passing.
It looks like this pull request may not have tests. Please make sure to add tests or get an explicit test exemption before merging.
If you are not sure if you need tests, consider this rule of thumb: the purpose of a test is to make sure someone doesn't accidentally revert the fix. Ask yourself, is there anything in your PR that you feel it is important we not accidentally revert back to how it was before your fix?
Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing.If you believe this PR qualifies for a test exemption, contact "@test-exemption-reviewer" in the #hackers channel in Discord (don't just cc them here, they won't see it!). The test exemption team is a small volunteer group, so all reviewers should feel empowered to ask for tests, without delegating that responsibility entirely to the test exemption group.
Thanks for the contribution! Marking as a draft for now since this will require min SDK updates, and that can't be done in the PR until the next stable has shipped.
It should be possible to update this to be landable now that 3.35 has shipped to stable.
From triage: @Phantom-101 Are you still planning on updating this PR to resolve the CI failures?
Sorry for the delay, I am currently busy with some other work so it may be a while before I update this.
Hey @Phantom-101 we came across this in triage. I really appreciate your work here, and totally understand your last comment about not being able to return to it right away. Since this has many merge conflicts now I am going to close it. Please do feel free to open a fresh PR if you decide to come back to this work. Thank you!