Skip to content

fix: update PluginApiClient URL construction for project context#1

Merged
pikann merged 1 commit into
masterfrom
fix/update-plugin-api-path
May 18, 2026
Merged

fix: update PluginApiClient URL construction for project context#1
pikann merged 1 commit into
masterfrom
fix/update-plugin-api-path

Conversation

@pikann
Copy link
Copy Markdown
Contributor

@pikann pikann commented May 18, 2026

This pull request updates the route structure in the PluginApiClient to make project scoping explicit in API calls, rather than automatically including the project in all plugin routes. The main changes involve removing the automatic /projects/{projectId}/ prefix from plugin routes and updating the documentation and code to reflect this new approach.

API Route Structure Changes:

  • The automatic /projects/{projectId}/ prefix is removed from plugin routes; project context must now be included manually in the path when needed. [1] [2]
  • Updated the documentation for PluginApiClient and pluginGet to clarify the new route structure and provide examples for including the project context. [1] [2]

API Client Interface Update:

  • The projectId property on PluginApiClient is now public to allow access when constructing project-scoped paths.

@pikann pikann merged commit fe4991e into master May 18, 2026
1 check passed
@pikann pikann deleted the fix/update-plugin-api-path branch May 18, 2026 08:44
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.

1 participant