Errors list sometimes links to "See:" annotation sites, not actual error sites

[ilkka]

For one project of mine, flow check outputs:

src/controllers/auth.js:49                                                                                                                                             
 49:   server.route(route.createPostRoute('/login', 'auth', {                                                                                                          
                    ^ call of method `createPostRoute`                                                                                                                 
 33:   config: RouteConfiguration                                                                                                                                      
               ^^^^^^^^^^^^^^^^^^ property `tags`. Property not found in. See: src/utils/route.js:33                                                                   
 49:   server.route(route.createPostRoute('/login', 'auth', {                                                                                                          
                                                            ^ object literal

The issue is totally valid, but the problem is that when I look at my Errors listing, it mixes up the "see also" and the actual error sites:

Instead of leading to src/controllers/auth.js, clicking on that errors leads me to where createPostRoute is defined, which is not helpful.

[gabelevi]

Would #47 fix this for you? It adds an error for each file mentioned in a Flow error.

[ilkka]

Yeah, I reckon it would! And if the entries appear in order, it would ensure the actual error site comes first in the list which is nice.

[orta]

#47 won't fix this I think, it would still show just one error.

in microsoft/vscode#1927 (comment) they show that you can have a multi-line description, but only with one line showing in the "problems" section.

So perhaps that is the key