Custom Plugin Settings

Bugs
1

I am working on developing a custom plugin and the plugin has some settings so I can configure it. You can see the settings in the following code:

import { Builder } from "@builder.io/react";
import ComplexLink from "./components/ComplexLink";
import {
  pluginId,
} from './utils';

Builder.registerEditor({
  name: "ComplexLink",
  component: ComplexLink,
  inputs: [
    {
      name: 'defaultType',
      type: 'string',
      defaultValue: 'model'
    }

  ],
});

//  Register the plugin itself with Builder, to define plugin options that the input type will reference
Builder.register('plugin', {
  // id should match the name in package.json, which is why we grab it directly from the package.json
  id: pluginId,
  // will be used to prefix generated types
  name: 'cms-link-plugin',
  // a list of input definition that you might need to communicate with custom backend API
  settings: [
    {
      type: 'text',
      name: "apiKey",
      friendlyName: 'Builder API Key',
    },
    {
      type: 'boolean',
      advanced: true,
      name: "showDebug",
      friendlyName: 'Show Debug Info',
    },
    {
      type: 'text',
      advanced: true,
      name: "models",
      friendlyName: 'Models',
      helperText: 'Provide a comma separated list of models to use in the model selector',
    },
  ],
  // Modify the save button text
  ctaText: 'Save Changes',
  // If we need to make a request to validate anything:
  // async onSave(actions) {
  //   appState.dialogs.alert("Plugin settings saved.");
  // },
});

However, when I load this plugin and then go to the plugins page, I don’t see this plugin to edit it’s settings. I also don’t see alot of the other standard plugins that normally appear. If I remove the plugin from my space all of the other plugins reappear on the plugins page.

I have included a video of my issue:

Recording-20241211_094722.webm

Here is a link to my github repo for the code:

[GitHub - jhs129/complexlink-plugin]

My space id I am using is: 9d9c17771b684627bed7d61d5f05ef44

2

Hello @jhs129,

We’ve reviewed the issue, and it appears to be specific to your implementation. I was unable to replicate the problem with another custom plugin, but I can confirm the issue does occur with yours.

We’re actively investigating the cause of this unusual behavior and will keep you updated with any progress.

Thanks,