You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Right now if the user creates a new .vala file and forgets to add it to meson, code completion doesn't work in the file and every type is interpreted as null. It's easy enough to recognise this and add the missing file afterwards, but I think it'd be nice if VLS issued a warning if the user edits a (new) .vala file that hasn't been added to meson yet. But of course this can be low-priority :)
To Reproduce
Source code repo:
Steps to reproduce the behavior:
Create new vala file
Start editing, all types show up as null <- Would be nice if VLS issued a warning here
Add to meson file
It works now
The text was updated successfully, but these errors were encountered:
I think we'd want to have VLS only warn you when you have errors that could be resolved by adding the file to the build system. Otherwise this could be annoying.
Perhaps what we'd want is for VLS to tell from the error messages when a certain namespace is being relied on that exists in one of the other projects that VLS knows about.
Describe the bug
Right now if the user creates a new .vala file and forgets to add it to meson, code completion doesn't work in the file and every type is interpreted as
null
. It's easy enough to recognise this and add the missing file afterwards, but I think it'd be nice if VLS issued a warning if the user edits a (new) .vala file that hasn't been added to meson yet. But of course this can be low-priority :)To Reproduce
Source code repo:
Steps to reproduce the behavior:
null
<- Would be nice if VLS issued a warning hereThe text was updated successfully, but these errors were encountered: