Documentation references are shown instead of the documentation.

The documentation is not shown correctly. Instead, we get the documentation reference.

For example, I want to know what TextField.autofillHints does. When I put the caret on top of some identifier and press Ctrl-Q, it should show the documentation. Instead, I get this:

{Iterable<String>? autofillHints}  

Type: Iterable<String>?  

{@macro flutter.widgets.editableText.autofillHints} 
{@macro flutter.services.AutofillConfiguration.autofillHints}

This basically forces us to search the internet for the documentation, defeating its purpose.

[stevemessick]

@marcglasberg It looks like you are using Flutter v2.2.3, which is old. I suspect the problem is fixed in more recent SDKs.

[stevemessick]

@marcglasberg That’s a really good question; I wish it had a simple answer. If you don’t know how something is implemented it is hard to know where to file issues. The Flutter plugin adds support for Flutter-specific features, but relies on the Dart plugin for everything specific to the Dart language. The Dart plugin was created by JetBrains, so that’s why Dart issues go in the JetBrains issue tracker. However, @alexander-doroshko at JetBrains is also really good at keeping tabs on issues filed here, so issues usually get moved around as needed. It is easy for us to move issues between Github repositories. The two most frequent destinations are dart-lang/sdk for Dart analyzer issues and flutter/fluter for Flutter SDK issues. It would be nice if there was an easy way to move issues to the JetBrains tracker, too.

The simple approach is to file issues here and let us figure out where they belong. Perhaps @devoncarew would have some insight here.