Repository navigation
[material_ui] Copies a11y_assessments - #12686
Conversation
There was a problem hiding this comment.
Code Review
This pull request introduces a new Flutter project, a11y_assessments, designed for accessibility testing across multiple platforms including Android, iOS, Linux, macOS, Web, and Windows. It implements a wide range of widget use cases to assess accessibility compliance, along with corresponding tests. Feedback on the changes highlights a potential compilation issue in utils.cpp due to the use of a non-standard macro UNICODE_STRING_MAX_CHARS, and identifies several unused variables in action_chip.dart, card.dart, and navigation_drawer.dart that should be removed.
|
reason for override: this is a sample app that won't be include in the release. |
QuncCccccc
left a comment
There was a problem hiding this comment.
LGTM. Just have a question, I saw the original app in flutter/flutter also have a GEMINI.md file, is it for agent learning? Just curious whether we also want that in material_ui.
I have no idea how it works, I think that is for gemini code assist, and I am not sure if it still working because the tech change fast. I will defer that to your team, but for now, I removed that file because packages repro doesn't have the same convention. |
|
We should pubignore this directory so it's not released with I also wonder if it would make sense to add it in a subdirectory (e.g. @QuncCccccc what are your thoughts here? |
|
Both suggestions make sense to me! |
|
ok i will put it in test_apps |
e6fb86f to
036f7b1
Compare
elliette
left a comment
There was a problem hiding this comment.
Thank you for updating the directory structure! Just one more change otherwise looks good.
There was a problem hiding this comment.
Could we keep these as separate pubignores in tool and test_apps? See discussion here: #12469 (comment)
Basically if we have a pubignore here, we will have to keep it in-sync with the gitignore which sounds error prone to me
There was a problem hiding this comment.
ah ok, the reason i moved it here is that the plugin tool only read the root pubignore, but looks like we shouldn't do that. will refer and see what to do
There was a problem hiding this comment.
I updated the ci to be able to pick up pubingore in this case
|
|
||
| /// True if this package is located within a directory that is ignored | ||
| /// by the enclosing package's `.pubignore` file. | ||
| /// by the enclosing package's `.pubignore` file, or by a `.pubignore` file in |
There was a problem hiding this comment.
cc @stuartmorgan-g , in case there is a good reason not to.
There was a problem hiding this comment.
I need this because I add a test app a11y_assessments to the material_ui, but the ci will read the pubignore only if it is in the root material_ui directory.
There was a problem hiding this comment.
I can't think of any reason not to support this, we just didn't need it before.
26c3f23 to
0df3700
Compare
elliette
left a comment
There was a problem hiding this comment.
LGTM! Thanks for fixing the isPubIgnored logic!
…r#192292) flutter/packages@f9b3954...9af9c60 2026-09-03 47866232+chunhtai@users.noreply.github.com [material_ui] Copies a11y_assessments (flutter/packages#12686) 2026-09-03 21270878+elliette@users.noreply.github.com [material_ui] Migrate M3 BottomSheet template to use new gen_defaults (flutter/packages#12731) 2026-09-03 21270878+elliette@users.noreply.github.com [material_ui] Migrate M3 ActionChip template to use new gen_defaults (flutter/packages#12732) 2026-09-03 bolling.ludwig@gmail.com [camera] Add setImageQuality for JPEG compression control (flutter/packages#11155) If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/flutter-packages-flutter-autoroll Please CC flutter-ecosystem@google.com on the revert to ensure that a human is aware of the problem. To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose To report a problem with the AutoRoller itself, please file a bug: https://issues.skia.org/issues/new?component=1389291&template=1850622 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
as title. Move the app in material gives us benefit that we can both fix accessibility issue and verify the fix on the app faster without waiting for a release cycle ## Pre-Review Checklist **Note**: The Flutter team is currently trialing the use of [Gemini Code Assist for GitHub](https://developers.google.com/gemini-code-assist/docs/review-github-code). Comments from the `gemini-code-assist` bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed. [^1]: Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling.
as title. Move the app in material gives us benefit that we can both fix accessibility issue and verify the fix on the app faster without waiting for a release cycle ## Pre-Review Checklist **Note**: The Flutter team is currently trialing the use of [Gemini Code Assist for GitHub](https://developers.google.com/gemini-code-assist/docs/review-github-code). Comments from the `gemini-code-assist` bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed. [^1]: Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling.
as title.
Move the app in material gives us benefit that we can both fix accessibility issue and verify the fix on the app faster without waiting for a release cycle
Pre-Review Checklist
[shared_preferences]///).If you need help, consider asking for advice on the #hackers-new channel on Discord.
Note: The Flutter team is currently trialing the use of Gemini Code Assist for GitHub. Comments from the
gemini-code-assistbot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.Footnotes
Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling. ↩ ↩2