Skip to content

Delete legacy inspector#9782

Merged
elliette merged 10 commits intoflutter:masterfrom
elliette:issue-9563-3
Apr 20, 2026
Merged

Delete legacy inspector#9782
elliette merged 10 commits intoflutter:masterfrom
elliette:issue-9563-3

Conversation

@elliette
Copy link
Copy Markdown
Member

@elliette elliette commented Apr 18, 2026

Work towards #9563
Fixes #9566

This PR:

  • Removes the option to switch to the legacy inspector
  • Remove all legacy inspector code
  • Moves inspector_shared files to inspector_v2

It does not:

  • Rename inspector_v2 to inspector (that will be follow up to avoid over-complicating this PR)

I recommend reviewing commit-by-commit since the Github diffing algorithm otherwise shows files as having been deleted and re-added when in fact they were simply moved.

@elliette elliette marked this pull request as ready for review April 20, 2026 19:29
@elliette elliette requested review from a team, bkonyi and kenzieschmoll as code owners April 20, 2026 19:29
@elliette elliette changed the title [Draft] Delete legacy inspector Delete legacy inspector Apr 20, 2026
Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request completes the transition to the redesigned Flutter Inspector (V2) by removing the legacy inspector code and the option to switch back to it. The changes involve deleting numerous legacy files, updating imports across the codebase, and consolidating the V2 implementation. Feedback focuses on critical type safety issues in the settings dialog where invalid casts to ValueNotifier<bool?> could cause runtime errors, along with suggestions for import consistency and safer disposal logic in the screen controller.

Comment thread packages/devtools_app/lib/src/screens/inspector_v2/inspector_screen.dart Outdated
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tried to fix the test here to force the images in the memory panel legend to lad, but wasn't successful. Didn't spend too long investigating because I know image rendering is unstable in screenshot tests (see flutter/flutter#38997) but can investigate more if needed!

Copy link
Copy Markdown
Contributor

@srawlins srawlins left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Love it!

@elliette elliette merged commit 46811ca into flutter:master Apr 20, 2026
46 of 47 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Delete legacy inspector code in DevTools

2 participants