Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Make analyzable file types customizable

See original GitHub issue

A plugin in the analysis server could support analysis results for file types that are neither Dart or HTML. For these files, DartCode wouldn’t send analysis requests to the analysis server because the file ending is not matched by isAnalyzable: https://github.com/Dart-Code/Dart-Code/blob/2ca8e876bd6080f856cbe6dc412a5ba37ac1bfbc/src/extension/utils.ts#L130-L134

Is there a reason not all files in the current workspace are marked analyzable? If there is, it would be amazing if we could make the analyzable file endings customizable. Then, plugins that support custom file endings could instruct users to mark the respective file ending as analyzable.

Issue Analytics

State:
Created 4 years ago
Comments:9 (9 by maintainers)

Top GitHub Comments

1reaction

DanTupcommented, Aug 26, 2019

I’ve added this new setting, which is an array of file extensions:

"dart.additionalAnalyzerFileExtensions": [
	"moor",
]

The current languages use the language ID, but I wasn’t sure if VS Code would assign them to unknown files, so this one uses the extensions (as returned by Node’s path.extname with the dot stripped off the front).

1reaction

DanTupcommented, Aug 26, 2019

Thanks for the info! For now, I think a user-supplied list probably makes the most sense - it’s the least risky if something is wrong because the user can easily turn it on/off without needing new releases.