Sam Deane

Actually, I've implemented relationships too, so that's not a problem - they are really just a different list of properties, that have a different template. We have the ability to...

I realise that this is likely a toolchain issue outside of your control. The main purpose of this report is as a breadcrumb for anyone else seeing the same behaviour!

> Thanks for the report @samdeane Can you take a look at [this](https://github.com/flutter/flutter/issues/121702) and check if it resembles your case or not ? Yes, I think that being able to...

> It sounds like you know a lot about this. We would certainly take pull requests to fix this, if it's a bug. 🙂 I hear you 😆. > We...

> Could this be a symlink instead of a script? You'd have to ask the author of the asdf Flutter support. > I'm not a fan of special-casing specific package...

> Btw - if this is specifically for your own use, is there a reason not to just click the "Locate SDK" button It's a bit of an ugly solution,...

> It seems like it might handle the issue without the drawbacks noted above? The problem is that setting a global env var rather defeats the point of asdf (which...

If one could persuade vscode itself (_not your plugin_) to evaluate `$(asdf where flutter)` in the context of the loaded workspace, that would be fine. I don't think that's an...

In the meantime I have workarounds so it's not the end of the world - it would just remove a little bit of friction :)

> Out of interest - in which cases are you hitting the issue where you're told the SDK is not found? For existing projects I would expect us to find...