boost graphql types in results

[keegancsmith]

Because "type" in scip-ctags matches so much we can't boost it as high as we do for classes/structs in our language specific boosting. In the case of GraphQL this is useful to boost.

Note: This work was guided by experimentation locally. Still need to set up a more robust way to track the effects of ranking changes.

Test Plan: A search like "type User" in the sourcegraph codebase now includes results from the schema.graphql files.

[jtibshirani]

Makes sense to me as an isolated change.

As you said, it'd be nice to have more of a framework for making these changes. I've also been pondering if there's a better way to unify things across languages, it's a bit tricky to have custom score factors per language.

[keegancsmith]

As you said, it'd be nice to have more of a framework for making these changes.

Yeah I think this is key. I may hack on simple snapshot testing here.

I've also been pondering if there's a better way to unify things across languages, it's a bit tricky to have custom score factors per language.

I think the problem here is that even though things have the same "concept" in different languages, the importance is language specific. My thinking here is we should put some work in to ensure equal footing so for example we don't constantly have go as the top result just because that is what we care about. Additionally I think a little bit of work providing a variety of results will go a long way here as well (so it isn't just strictly sorted on score).