Add new "Go to Import" option

[FMorschel]

I'd like to propose a "See import line(s)" on classes/methods from classes or extensions/functions/global variables.

Like:

import 'dart:math';

void main() {
  max(1, 2);
}

In the above example, there would be a way to access this in the "max" and it would take you to the import line (here you could alias it or whatever).

And if there was a conflict between multiple imports it could select all with multiple cursors.

[dart-github-bot]

Summary: The user proposes adding a "See import line(s)" feature that allows users to navigate from a class, method, or variable to its corresponding import line, even when multiple imports exist. This feature would enhance code navigation and understanding.

[keertip]

@FMorschel , how does this show up in the editor? Context menu? Code actions (an option in the light bulb menu)?

[FMorschel]

@keertip the current CL (https://dart-review.googlesource.com/c/sdk/+/387387) should work with an action on the context menu. Similar to the Go To Super option.

class A {}

class B extends A {}

If you right-click on B you will get an option Go to Super Class/Member. It will change your selection to the declaration of A.

It would be something like this but with an optional list to see all imports. Similar to the "References" (F12) on VS Code where you can see every call to something, you would be able to see all imports that are importing that specific name.

For the following case, both imports would show if you called it on StatelessWidget, Widget, BuildContext or Placeholder.

import 'package:flutter/widgets.dart';
import 'package:flutter/material.dart';

class MyWidget extends StatelessWidget {
  const MyWidget({super.key});

  @override
  Widget build(BuildContext context) {
    return const Placeholder();
  }
}

@DanTup is there anything else?

[DanTup]

Yep, that sounds right to me. Note that it will require Dart-Code changes, it won't show up anywhere automatically. We can also choose whether it's in the context menu or not, or only in the command palette (the context menu is good for discoverability, but it's not particularly contextual in the VS Code editor, so opening the context menu anywhere will show it, even in blank spaces and comments).

[bwilkerson]

@jwren @alexander-doroshko

This is functionality that I think we should have in IntelliJ as well. I think it will be even more important when 'enhanced-parts' ships because there will potentially be multiple lists of imports spread across multiple files, making it harder for users to figure out where a given name is imported from.

The current implementation defines a custom LSP protocol for this purpose. I don't know whether that would be sufficient for IntelliJ, but I'd appreciate it if you could think about it and let me know what kind of support would be required.