[go_router_builder] Fix #106121 and #116837 - Fix compile error on the generated code when using $extra and non nullable enums queryParams
Issues Fixed: https://github.com/flutter/flutter/issues/116837
Relevant https://github.com/flutter/flutter/issues/106121
Pre-launch Checklist
- [x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
- [x] I read the Tree Hygiene wiki page, which explains my responsibilities.
- [x] I read and followed the relevant style guides and ran the auto-formatter. (Unlike the flutter/flutter repo, the flutter/packages repo does use
dart format.) - [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 listed 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 this PR is exempt from version changes. - [x] I updated
CHANGELOG.mdto add a description of the change, following repository CHANGELOG style. - [x] I updated/added relevant documentation (doc comments with
///). - [x] I added new tests to check the change I am making, or this PR is test-exempt.
- [x] All existing and new tests are passing.
If you need help, consider asking for advice on the #hackers-new channel on Discord.
It looks like this pull request may not have tests. Please make sure to add tests before merging. If you need an exemption to this rule, contact Hixie on the #hackers channel in Chat (don't just cc him here, he won't see it! He's on Discord!).
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.
I also think there's room for improvement on how extras are handled.
I'll work on a new issue with proposed changes, I've got a couple of ideas to make improve DX.
We can discuss that and eventually implement it
@dancamdev Are you planning on updating this PR based on the feedback above?
Sure, hopefully I find time this week
Meanwhile is there any workaround we can use here?
@dancamdev are you still planning on coming back to this pr?
The ci is failing, can you fix the failing test?
(triage) Hi @dancamdev are you still plan to work on this PR? If not we can close this PR for now and reopen when you have time to work on it.
It looks like tests are timing out on my end.
Getting this error on Windows
hell: [ERROR:flutter/shell/common/shell.cc(89)] Dart Error: error: import of dart:mirrors is not supported in the current Dart runtime
Shell: [ERROR:flutter/runtime/dart_isolate.cc(144)] Could not prepare isolate.
I'll try to run it on Linux and see if that works
@dancamdev Are you still planning on updating this to address the test issue?
Hi @dancamdev I will close this pr for now. Feel free to reopen once you have time to work on this