How do we add new supported languages?

[Lawouach]

Heya,

I'm interested in supporting peripheric languages such as toml or yaml. How does on go about adding them?

Thanks,

[timonv]

Hey @Lawouach,

How do you intend to use it?

The SupportedLanguages in swiftide-integrations/src/treesitter are just for the latter. We use treesitter for the following:

• Semantic chunking
• ref/def extraction as metadata
• outline extraction as metadata

The first one is fairly straightforward. Just adding the language to supported languages should be enough. For the other two, we generally copy the queries in the grammar library for that language, and slightly modify them so they give the right results.

That said, if you just want to index yaml/toml unstructured with swiftide, you can just do it and see how that goes.

[Lawouach]

Hey @timonv

I'm a bit confused but that's on me :)

I'm trying to figure how to benefit from indexing::transformers::OutlineCodeTreeSitter::try_for_language but, as I read the code, it seems to expect a language found in the SupportedLanguages enum, right?

So, is there a constraint for that enum to limit the languages that are supported? If so, can I still use the OutlineCodeTreeSitter transformer with other languages?

[timonv]

Hey @Lawouach,

That is correct. It uses tree-sitter to generate the outline. Ironically, not all languages in SupportedLanguages are fully implemented. It will give an unimplemented if that's the case.

[Lawouach]

I see. So perhaps my best course of action, to adjust to my uses cases, would be to re-implement OutlineCodeTreeSitter to match my needs?

As a side note, I really enjoy working with swiftide. It's well design and it does what I need. Perhaps my only concern is its documentation which meant I had to grope for the right approach a few times. But overall, I like it :)

[timonv]

Thank you! What is your usecase? I'd love to think along.

Are there any specific parts in the documentation that you are missing or found misdirecting?