When u write print(@"$a") everything is fine and a has a different color from the color of the string.
But if you write print(@"$(a.b)") (a.b) now have the same color.

the regexp ^(.*):(\\d+)\\.(\\d+)-(\\d+)\\.(\\d+):\\s+(warning|error):\\s+(.*)$ is doing fine for finding error messages from valac but it doesn't do so well at warnings. I got the the following warning about a deprecation and the format of the line is quite different: /home/singingbush/gtkproject/src/myapp-gtk.vala:22:2: warning: ‘gtk_color_button_set_rgba’ is deprecated: Use 'gtk_color_chooser_set_rgba' instead

the following should work in this scenario ^(.*):(\d+):(\d+):\s+(warning):\s+(.*)$

perhaps instead of just having a $valac problemMatcher there could be $valac-errors and $valac-warnings. That also gives the user more control about what they want to match on: "problemMatcher": [ "$valac-errors", "$valac-warnings" ]

Hello im newbie in all this vls and vala, in the description of the plugin when installing it from extensions vs code states that it is better to use libvala for autocomplete and better forming.
So, how to do it?

I'm not sure this is the right "level" to tackle this issue, please let me know if it's not.
In .vapi files you can have a lot of [Version ...] codes, which I think are usually a bit less important than the other code. They can make vapi files quite hard to read when there are a lot fo them. One example:

https://github.com/elementary/gala/blob/1024813560668152814a72fd93dc6a93b226eb04/vapi/mutter-clutter-1.0.vapi#L4715-L4730

Would there be a way to slightly dim (visually less important) these [Version ...] codes? A bit like what happens with comments for example?

Please update Main Entry Point snippet

https://wiki.gnome.org/Projects/Vala/ValaForJavaProgrammers#Main_Entry_Point

Hi,
i forked your repo and put it on work with vls and gvls they work both well (at least error, warnings and reference to declaration.

What do you think about merge one of them into the master?
of course the vls integration need more work but for now it could be enough.

in vala-code/package.json the problemMatcher uses "fileLocation": "absolute" which ends up in file not found when clicking on the problem. I think it should be:

"fileLocation": ["relative", "${workspaceRoot}"],

Problem:

Code:

public class Person : Object {

    /* Construction properties */
    public string name { get; construct; }
    public int age { get; construct set; }

    public Person(string name) {
        Object(name: name);
    }

    public Person.with_age(string name, int years) {
        Object(name: name, age: years);
    }

    construct {
        // do anything else
        stdout.printf("Welcome %s\n", this.name);
    }
}

happy to help - but just starting vala education after several other OO languages
will help where i can

Link to benwaffle/vala-language-server for Visual Studio Code.

it cannot find namespace Gtk

error message is :
this namespace name Gtk couldnot be find

When you create a new instance of generics type whose namespace does not have any periods (like <string>, <int>, or <FooBarList>), List<string> is colored with blue.

However, when you create a new instance of generics type whose namespace has periods (like IBus.Bus or FooBarList.FooBarListRow), the last > is not colored correctly.

would need to add something like this to the contributes section of package.json and some code to sit between GDB and the vscode API.

https://code.visualstudio.com/docs/extensions/example-debuggers

"debuggers": [{
    "type": "gdb",
    "label": "GDB",
    "windows": {
        "program": "C:\\MinGw\\bin\\gdb.exe"
    },
    "osx": {
        "runtime": "gdb"
    },
    "linux": {
        "runtime": "gdb"
    }
}]

I realise it's probably a big job but it's certainly doable. The D plugin makes use of gdb so it may be possible to reuse some of its code:
https://github.com/WebFreak001/code-debug/blob/master/src/gdb.ts

This is something that'd be immensely useful when developing.

Here is an implementation for the PHP plugin

Happy to help if you require any help with this.

after "Hit F5 in VS Code " i get that

and that