Skip to content

Fixed path handling for plugins#608

Merged
igor84 merged 2 commits intomasterfrom
plugin-api-fix
Dec 17, 2023
Merged

Fixed path handling for plugins#608
igor84 merged 2 commits intomasterfrom
plugin-api-fix

Conversation

@igor84
Copy link
Collaborator

@igor84 igor84 commented Dec 14, 2023

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.

@igor84 igor84 requested review from JoC0de and popara96 December 14, 2023 09:30
@igor84 igor84 merged commit f671396 into master Dec 17, 2023
@igor84 igor84 deleted the plugin-api-fix branch December 17, 2023 11:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

Comments