for live edit, I noticed that an import is conside...

# compose-android

[agrosner]

for live edit, I noticed that an import is considered an incompatible change so the state goes to “paused”. However if I add a single line in the file and save, then it considers it “compatible” and updates and seems to work correctly. Why does live edit consider imports breaking, but then works with this workaround?

[jw]

An import could change resolution of any extension function or type anywhere in the file.

[Alan Leung]

Yep. It is exactly what Jake Wharton said. Import can change resolution quite a lot.

The issue isn't that we can't Live Edit an import change, the main problem is that it doesn't know what to recompose.

A full invalidate state and recompose would have solve that issue but your app constantly losing states gets annoying quickly. The current state is we "paused" the import edits for you.

Like you said, the work around is just simply add a white space or continue your edits. Live Edit will only invalidate that function you added a space to instead.

[Alan Leung]

Our team is working on removing this restriction and you should be able to change import without the intermittent "Pauses".

In fact, that is the current behavior if you are using Studio Iguana Canary 1.

[agrosner]

sorry for long response time. recently this came back as ive used live edit a bit more lately:
i notice this happens when importing things compose should know about such as basic modifiers and alignment types. this hinders the DevX in Giraffe. glad to see that iguana will fix it - will switch to it and try it out. thanks