Hi I'd like to tell you about an exciting new feature in gitlab 13.1 code intelligence code. Intelligence is something we're probably all familiar with from working in our local development environments. When you hover over a function, you often can get a definition see where it's defined and find other references to that function and in 13.1 we're adding our first version of code intelligence, which includes the simple documentation and go to definition we're building on top of the language.

So the index format which comes from language service and source graph, has done a lot of great work on this, and we want to make it easy for everyone to access this information, and we've done that in a really simple and easy way that I'd like to show you. But first let me show you how the feature looks once it's configured, here's a side, project I'm working on, and if we go to one of the files, we can see that there's now a whole lot of symbols that are underlined, and this means there's code intelligence.

If I click on it, I'll see a definition. In this case there isn't one. But I can go to sorry documentation, but I can go to the definition to learn more and see it's defined up here. This was defined in a different file. It would take me directly to that file. I can go to a more complicated file where I've got some junior stock tags and they also are understood by this language. Server, fire language survey index generator, but you're like language like NGO, might support a different kind of documentation format.

So here I've added some tags and if I click I can see that I've now got some type annotations, which I otherwise wouldn't get, and if I click on a argument, I can see the argument documentation it's coming from here. So I set this up using the else if node project, which is maintained by source graph. Thanks for your work on this one- and it only took me about 30 seconds- to enable this and configure it correctly.

In my gitlab CI ml file, I created a new CI job called code intelligence, but you can call it whatever you'd, like the important thing that it does.

Is it generates an else--if file, the default output of the library that I'm using is dumpin elsif and importantly, what I've done is I've declared an else--if artifact and that tells the gitlab CI runner to process this file and do something with it and that's important, because that's how we get the code intelligence out of the CI job and in ticket lab, and so the command itself was one line very simple. We run the elsif generator I provide the path to my source code in this project.

In this case it's the Lib directory and the test directory, so I get coverage across them all of my source code and then I need a few extra arguments, because this is a JavaScript project and not a typescript project and then I also needed one additional dependency, which is the node else. If generator, that's all I needed to do the jobs. Very quick and now I've got code, intelligence, we'd love to hear your feedback really excited about this improvement and we hope to add support for more languages in the future.

But let us know how you go and please check it out.