Theia: files.associations does not work

Created on 26 Mar 2019  路  8Comments  路  Source: eclipse-theia/theia

```
"files.associations": {
"*.go": "typescript"
}
````

An editor for *.go languages should prefer typescript language, it does not.

bug editor filesystem

All 8 comments

Hey @akosyakov, I've been sort of following along with this issue but I was hoping you could clarify some thing for me. If I understand the current state, it seems that the files.associations setting was added by #4713 but it is not yet functional after #4721? I'm curious because don't see the files.associations option in setting at all when I spin up the lates version of Theia 0.5.0-next.9043bc1d.
Do you have any idea when this implementation might be functional?

Thanks for the help on this, I appreciate it!

It was not introduced yet, it was stubbed to make VS Code extensions to load. An implementation is tracked in https://github.com/theia-ide/theia/issues/4581.

Do you have any idea when this implementation might be functional?

@tolusha could you help to answer please

@jonnyhork
As @akosyakov mentioned an implementation is tracked in https://github.com/theia-ide/theia/issues/4581
My initial plan was to fix extension loading https://github.com/theia-ide/theia/pull/4721
For the time being I postponed the issue https://github.com/theia-ide/theia/issues/4581

Ok thanks @tolusha , I'll keep an eye on #4581.

For the time being I postponed the issue #4581

Does this mean there is currently no plan to continue work on the implementation at the moment?
I'm asking just so I can have a better understanding of the timeline for custom file associations and plan accordingly.

We'll get back to it in our next sprint (starting week after next)

@tsmaeder Hi, I just wanted to check in about this issue. I see that file.associations was added to this sprint but I am hoping you could speak to and estimated time for implementation. This would help me decide whether to use a workaround solution depending on the timeline. Thanks again for your help!

@jonnyhork
I would suggest using workaround for now.

Was this page helpful?
0 / 5 - 0 ratings