Make LanguageManager test for built-in languages more flexible

[redmunds]

Test is: "should support built-in languages".

Currently, it tests for an exact match of file extensions, so any time a new language is added the test fails.

One solution is to make sure each file extension listed exists, but entire list does not need to be an exact match.

[njx]

In general, it would be better to make the LanguageManager unit tests inject mock data instead of relying on the real languages.json file loaded into Brackets.

[njx]

Marking starter bug. The simple fix we want is to just make it so the unit test checks for a few extensions that we know should be on the list, but not fail if other extensions happen to be on the list as well.

[thefirstofthe300]

So I am wanting to work on this issue and am wondering what I am looking at.

I am very familiar with vanilla JavaScript but don't have very much experience with all of the different JavaScript frameworks. Is the expect function from the Jasmine framework? I am only guessing because of a Google search.

Edit: Just found the Jasmine call. Disregard above.

[redmunds]

Ooops, didn't mean to close. You can find Jasmine documetnation here: http://pivotal.github.io/jasmine/

[thefirstofthe300]

As I am running on a Linux-only machine, I am having trouble getting the unit-tests (and a few other things) to work correctly. Because of this I am not able to test my code myself.

Is the problem when you add a file extension to the file extension list or when you add a whole language to the language.json?

[thefirstofthe300]

I think that this should fix the problem. Due to difficulties getting unit-tests to run for Linux, I am not able to test this myself.

[redmunds]

Fixed. Closing.