Support for per project Flutter SDKs.

[pq]

A breakout from #54.

In an ideal world we should support per-project (or in IntelliJ vernacular per-module) SDKs.

[sethladd]

s/ideal world/by the time flutter makes a push for external usage :)

[pq]

cc @jwren for Dart Plugin ramifications
cc @bwilkerson for Analysis Server implications

[alexander-doroshko]

Tracked as https://youtrack.jetbrains.com/issue/WEB-20870, planned for 2017.1

[mit-mit]

Tracked as https://youtrack.jetbrains.com/issue/WEB-20870, planned for 2017.1

Does that include the 'per-project sdk' approach, or the workaround with the combo boxes?

[alexander-doroshko]

Combo is already there in the Dart plugin, but changing SDK in one project affects all others.
So yes, that request is for true per-project sdk approach.
But at this point it is not about SDK per-module in multi-modular IntelliJ IDEA project.

[sethladd]

Great to hear!

…

On Mon, Dec 19, 2016, 2:36 AM Alexander Doroshko ***@***.***> wrote: Combo is already there in the Dart plugin, but changing SDK in one project affects all others. So yes, that request is for true per-project sdk approach. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#56 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAAVZ-bH4Vab5ALNeU5-RGYwZTPLeKwjks5rJl4OgaJpZM4JrKss> .

[pq]

Being tracked in https://youtrack.jetbrains.com/issue/WEB-20870.

[mit-mit]

Opened #822 to make sure we get the full end-to-end experience for this completed and verified when 2017.1 ships.