Should also index other languages, like TypeScript, JavaScript

Apr 9, 2014 at 9:46 AM
Hi.

Usually projects use a mix of different languages (for example HTML, TypeScript, JavaScript for frontend) and C# for backend.

Hence to be really a universal the tool should provide more broader support for languages.
Is there any reason why indexing can not cover other types of source files?

BR, Gianni
Apr 9, 2014 at 1:31 PM
Usually projects use a mix of different languages (for example HTML, TypeScript, JavaScript for frontend) and C# for backend.
You're absolutely right!
Hence to be really a universal the tool should provide more broader support for languages.
Agreed!
Is there any reason why indexing can not cover other types of source files?
In a word, resources.

To index a new language our normal process is to parse the language, index each language construct (e.g., each method, field, class, etc), and then search. Thus, for each of these new languages we'd need a parser to be implemented that created Lucene docs for each language construct. This takes a bit of effort, and we don't have enough contributors to do that now, especially for multiple languages.

However, we could index all "unknown" files as a single document. This would provide worse results for those non-supported languages, but at least they'd have results. What do you think of this approach? We've been considering it for some time but were unsure what users would think....