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
I hit an issue where find all reference was not working. I identified the issue as being due to getProjectFileAutoGuess only search upto 2 directory levels, which meant it was not reaching the .nimble file directory, and so had to use a less certain method than nimble dump to identify the project file. This led to the wrong project file being guessed, which broke the referencing functionality. I wrote about it all at: https://forum.nim-lang.org/t/12538#77190.
It can be fixed simply by uping the number of directory levels the autoguessing travels in search of the .nimble file. In my local langserver repo I upped it from 2 to 10 to get things working.
Do you want me to create a pull request with my change?
The text was updated successfully, but these errors were encountered:
Sure, go ahead. Although a better solution would be to make nimble dump work in subfolders.
In any case, make sure to add a test case showcasing your issue in tprojectsetup.nim
Hello,
I hit an issue where find all reference was not working. I identified the issue as being due to getProjectFileAutoGuess only search upto 2 directory levels, which meant it was not reaching the .nimble file directory, and so had to use a less certain method than nimble dump to identify the project file. This led to the wrong project file being guessed, which broke the referencing functionality. I wrote about it all at: https://forum.nim-lang.org/t/12538#77190.
It can be fixed simply by uping the number of directory levels the autoguessing travels in search of the .nimble file. In my local langserver repo I upped it from 2 to 10 to get things working.
Do you want me to create a pull request with my change?
The text was updated successfully, but these errors were encountered: