Fixed path handling for plugins by igor84 · Pull Request #608 · GlitchEnzo/NuGetForUnity (original) (raw)

Turns out I didn't properly handle the plugin path. I didn't make sure that it is saved as relative path and that it was turned into an absolute path when used in Cli version.

I also updated main workflow to use new net8.0 LTS for packaging nuget packages which will also means that Cli version will require it to run from now on instead of net7.0.

Besides that I also exposed INugetPackageIdentifier.Version and INuspecFile.Id setters to plugins so they can modify the default nuspec file for new packages. Another such thing is PackageInstallDir that is now exposed on INugetPluginService.

UninstallAll method is made public instead of internal so users can for example add a menu item for it if they want.

Lastly I added one more extension point for handling found installed packages when they are loaded from PackageInstalledDir or RepositoryPath as we call it in NugetConfigFile.