Danny Tuppeny

> ran into this. It might be familiar to you :) Indeed 😄 That one is really a fallback I'd prefer not to use though. We could already work around...

> What would be the most relevant LSP issue to participate in? This depends a little on the specifics of what you want to do. Using your example from above...

@bwilkerson > Ideally I'd like to see them add general refactoring support that would allow servers to specify, for each refactoring, a set of parameters that users need to provide,...

My understanding is that we can't run the tests in the SDK with `dart test`, as it triggers `pub` to run and breaks things. And as far as I know,...

Ooh, possibly. Though the comment says: > Allow pub get/upgrade to run on a number of packages in pkg/ If it only works for _some_ packages, it may be hard...

> Are those the requirements for the Run | Debug links to appear in more places? To clarify - the reason we need to use `dart test` (or `pub run...

@nshahan sorry I wasn't very clear. There is a rule in the Dart-Code extension that detects the SDK and specifically disables this functionality because it's not guaranteed that running `dart...

That sounds reasonable to me. From the IDE, I don't think a user would really expect running a test to trigger a package fetch anyway (if things are out of...

Is this request related to the _Type_ Hierarchy or _Call_ Hierarchy? There's an open issue at #612 for call hierarchy. I'd agree it makes sense to move the Type Hierarchy...

This is implemented by https://github.com/dart-lang/sdk/commit/6f8d1e4859b4052094f2f492aa596b8f6364a412. It ships in the Dart language server so will show up with a future SDK release (not a Dart-Code release).