Open
Description
This is the tooling side of the issue of flutter/website#3566. Various statement management packages apparently have different implications to what code becomes reloadable, and some of the behaviors are not expected by app developers. It would be great if the IDE can help the user in two ways:
- Let users know when they wrote code that is not going to run after hot reload
- Let users know how they can tweak their code to make it hot reloadable.
Maybe we can try out a few statement management packages in the next team hackathon?