Skip to content

fix: fixed project initialization not allowing access to the plug-in … #1163

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 6, 2024
Merged

fix: fixed project initialization not allowing access to the plug-in … #1163

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion ui/src/utils/pluginKit/index.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,7 +56,8 @@ class Plugins {
async init() {
this.registerBuiltin();

const plugins = await getPluginsStatus().catch(() => []);
// Note: The /install stage does not allow access to the getPluginsStatus api, so an initial value needs to be given
const plugins = (await getPluginsStatus().catch(() => [])) || [];
this.registeredPlugins = plugins.filter((p) => p.enabled);
await this.registerPlugins();
}
Expand Down Expand Up @@ -169,6 +170,7 @@ const validateRoutePlugin = async (slugName) => {

const mergeRoutePlugins = async (routes) => {
const routePlugins = await getRoutePlugins();
console.log('routePlugins', routePlugins);
if (routePlugins.length === 0) {
return routes;
}
Expand Down