Support normalized visual capture bridge metadata#104
Conversation
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Hi! Thank you very much for your PR, could you kindly advise - is it ready for review/merge or you are planning to add something ? |
Summary
supportedKindsfrom normalized resourceparameterssupportedKinds, payloadsupportedKinds, and list content{ "parameters": { "supportedKinds": [...] } }Root cause
Some app-side MCP toolkit resources return
supportedKindsas regular result parameters. The dynamic resource gateway normalizes those values into JSON content underparameters, so the visual capture bridge can fail to detect an installed app bridge even thoughpermission_statusand the underlying screenshot extension are available.Validation
dart format mcp_server_dart/lib/src/capabilities/visual_capture/visual_capture.dart mcp_server_dart/test/visual_capture_test.dartdart test test/visual_capture_test.darton this checkout because current local Dart is3.11.5whilemainrequires>=3.12.0 <4.0.0.I also validated the same regression shape against the local v3.1.1 build workspace before opening this PR.