Sarrus1 / sourcepawn-studio

VSCode extension for SourcePawn scripting

https://sarrus1.github.io/sourcepawn-studio/

MIT License

147 stars 23 forks source link

mainPath issues #283

Closed ProjectSky closed 1 year ago

ProjectSky commented 1 year ago

if mainPath is not set the extension will not work
warning Invalid MaintPath setting. Please make sure it is valid.

Basic informations

OS: [Windows]
VSCode version: Latest
Extension version: 5.0.4

previous version (4.2.4) work fine even without set mainPath, this is a bug?

Sarrus1 commented 1 year ago

Should be fixed in v5.1.0.

I accidentally triggered a release instead of a pre-release.

Alienmario commented 1 year ago

I am still getting similar issue with latest version.

Starting SourcePawn server version 0.9.7
Received config ... "mainPath": String("") ...
thread 'main' panicked at 'Main Path does not exist.', src\server\files.rs:113:49
stack backtrace:
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
[Error - 6:21:49 PM] The SourcePawn Language Server server crashed 5 times in the last 3 minutes. The server will not be restarted. See the output for more information.

ProjectSky commented 1 year ago

in latest version if not set mainpath extension will not work. i choose to rollback to 5.1.0 version.

MainPath was not set and was automatically infered as xxx.sp.

Sarrus1 commented 1 year ago

Fixed in https://github.com/Sarrus1/sourcepawn-lsp/commit/943dc5a5d81cc4b028653f9fd277d287934ebcfc.

Alienmario commented 1 year ago

Now getting MainPath was not set and was automatically infered as playercommands.sp. even though i'm editing a different file. Right clicking a file and setting as main bring up the same notification.

Most features don't seem to work yet. I do have a few large projects opened as folders in my workspace. LMK if you need a test dummy. Otherwise i'm gonna stick with 4.x for now, which still works very well.