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
Simple as the title.
Basically, allow nimlsp to understand that some variables are pre-defined by nimble, and they should not be hinted as errors in the code.
The text was updated successfully, but these errors were encountered:
I designed this feature but never got around to implement it. Basically my idea was that you could define a preamble for certain file extensions. When nimlsp opens a file it would have a look at the installed preambles and see that it has a .nimble preamble. Then for each .nimble file it would append the preamble before processing the file. This would require some trickery to get line numbers correct, but apart from that it shouldn't be too hard to implement if someone wants to give it a whirl. Bonus points of course if there is some way a Nimble file can define their own templates so that if a program uses NimScript as a configuration language NimLSP would just automatically discover the template amongst your installed packages and provide support for that format.
Simple as the title.
Basically, allow nimlsp to understand that some variables are pre-defined by nimble, and they should not be hinted as errors in the code.
The text was updated successfully, but these errors were encountered: