Skip to content

Fix/devtools popup menu material UI - #702

Open
desmonddak wants to merge 9 commits into
intel:mainfrom
desmonddak:fix/devtools-popup-menu-material-ui
Open

Fix/devtools popup menu material UI#702
desmonddak wants to merge 9 commits into
intel:mainfrom
desmonddak:fix/devtools-popup-menu-material-ui

Conversation

@desmonddak

Copy link
Copy Markdown
Contributor

Description & Motivation

We are migrating devtools to use the latest analysis options and discovered some deprecated symbols.
Also, we found a Javascript file was needed in the shared widget support area for future widgets (module_info.js)

Related Issue(s)

None

Testing

Ran existing tests.

Backwards-compatibility

Is this a breaking change that will not be backwards-compatible? If yes, how so?

No

Documentation

Does the change require any updates to documentation? If so, where? Are they included?

None needed. This is lint cleanup, moving away from deprecated Flutter classes, and centralizing a resource file.

desmonddak and others added 9 commits August 27, 2026 05:52
Use material_ui popup menu entries in the shared DevTools widget helpers so consumers using material_ui showMenu receive compatible types. Keep Flutter Material test harnesses for native dialog localization and assert the returned popup types.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Track Flutter's generated exclusions for build and platform directories so dependency resolution does not leave the package worktree dirty.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Store the module-info helper in rohd_devtools_widgets so the schematic and waveform extensions can package the same implementation from either a local or Git package source.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This pulls in Dart 3.12 or above, which formats differently.
To avoid churn due to formatting as we have downstream PRs, we lower-bound to
Dart 3.6 for now, eventually 3.13.
Hopefully this threads the needly on formatting and deprecation until we can
do an en-masse reformat once PRs are resolved.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant