Don't include *.yaml files in 'analysis.analyzedFiles' notification.

Don't include *.yaml files in 'analysis.analyzedFiles' notification.

R=brianwilkerson@google.com, jwren@google.com
BUG=

Committed: https://github.com/dart-lang/sdk/commit/78f78feaf813120a0c2ef06733ec4aa887e346f9

[jwren, 2017-07-11 21:12:00]

On 2017/07/11 21:05:33, scheglov wrote:

LGTM

[scheglov, 2017-07-11 21:19:19]

Description was changed from

==========
Don't include *.yaml files in 'analysis.analyzedFiles' notification.

R=brianwilkerson@google.com, jwren@google.com
BUG=
==========

to

==========
Don't include *.yaml files in 'analysis.analyzedFiles' notification.

R=brianwilkerson@google.com, jwren@google.com
BUG=

Committed:
https://github.com/dart-lang/sdk/commit/78f78feaf813120a0c2ef06733ec4aa887e346f9
==========

[scheglov, 2017-07-11 21:19:21]

Committed patchset #1 (id:1) manually as
78f78feaf813120a0c2ef06733ec4aa887e346f9 (presubmit successful).

[Brian Wilkerson, 2017-07-19 17:12:38]

My expectation is that `analysis.analyzedFiles` would be used by clients to know
which files should be considered priority files when opened and which files to
send content overlay for. (If that isn't the case, then what is it being used
for?)

We are adding support for analyzing analysis options files. I would like clients
to know to send content overlays for these files, so, if my assumption above is
correct, I want them to be included in the notification.

I also have concerns about the potential implications of this approach for our
plugin support.

It seems to me that a better solution would be to put this filter in the
IntelliJ plugin rather than in server, given that IntelliJ is using this
information for a non-generic purpose.