John Ryan
John Ryan
These are implemented in the analysis server here * https://github.com/dart-lang/sdk/blob/main/pkg/analysis_server/lib/src/services/snippets/dart/flutter_stateful_widget.dart * https://github.com/dart-lang/sdk/blob/main/pkg/analysis_server/lib/src/services/snippets/dart/flutter_stateless_widget.dart
I'm going to close this for now - please comment if you are still seeing issues. This is likely related to Wasm.
Right now, the best way is indeed to use ctrl-z, but it would be great to have a history panel that allows users to roll back to a specific version.
Hi @kaushikbh99, can you describe more what developer scenario you are trying to document? Is there an API that you are using that we currently don't give enough visibility on?
cc: @devoncarew @parlough
I'm going to close this for now - this could be related to the Wasm support in the browser you are using.
Thanks for filing an issue, for this type of thing, we recommend using DevTool's [Highlight Repaints](https://docs.flutter.dev/tools/devtools/inspector#highlight-repaints) feature on an app running using a local version of Flutter.
Sorry, I misunderstood the issue. We should make sure we're efficiently rebuilding widgets, thanks for digging in.
I think the solution here would be to restrict what code can be injected into the _execution_ iframe, not the DartPad embedded iframe.
FYI @malloc-error