Trigger hot-reload and dartanalyzer on flutter sources change

I discovered the other day that hot reload works even when editing flutter sources from another project. That’s really cool for contribution. But Dart Code doesn’t handle it nicely for now.

Few things are missing :

• when having hotReloadOnSave to true, modifying flutter sources should trigger a hot reload.
• dartanalyzer doesn’t run on flutter source when opening an external project.
• dartanalyzer within the opened project doesn’t detect flutter changes ; unless window is reloaded.
• breakpoints inside flutter works ; but pressing f10 return to the project instead of just going by one line.

With these fixed we’d have a super cool contributing workflow.

[rrousselGit]

Oh, yeah. Sorry I forgot

Are you planning on contributing/committing the changes ?

That’s the idea. I used the “workspace” as a workaround.

Although I think Dart Code should handle edits inside Flutter folder without workspaces. As the reason we are using workspaces for mono-repo don’t really apply to flutter sdk.

Maybe not handle the whole flutter folder. example folder or similar are exceptions. But at the very least, the main package should be handled.

[DanTup]

Closing this as I think the solution is to add the flutter folder to your workspace if you want it to be tracked for reloading. Implementing it by watching all files would be technically complicated (and probably fragile) and I think it’s a very uncommon use-case to not want to do this.

I do think Code could do better here though, and the issues linked above are probably the best way to resolve that. You should 👍 those issues to help them along!