Testing locally

A plugin source is a public GitHub repository. That’s the only shape the installer resolves, so the iteration loop below is built around it.

The loop

1. Push your plugin repository to GitHub.
2. In Filer, open Connect, click the Manage sources button at the bottom of the plugin list to open the Plugin Sources panel, paste the repository URL into the URL box, and click Add.
3. Your plugin appears in the list under the All filter — select it and click Install.
4. Try it in chat, in a folder.

To pick up a change: edit, commit, push, then in Filer click Check for updates at the bottom of the plugin list, switch to the Updates filter, select the plugin, and click Update.

To start clean — for example after renaming a plugin or restructuring the repository — remove the source with the Remove source button beside its entry in the Plugin Sources panel and add it again, rather than trying to update in place.

Where to look when something is wrong

• Anything your handler logs through ctx.log.info / warn / error shows up in the app log.
• If the manifest itself fails validation, the plugin is refused at load and the app lists one message per broken rule — read all of them, not just the first, since a manifest can fail more than one rule at once.

Next

• Tools — result shapes to check for once a call is going through
• Permissions — the most common reason a call is refused rather than erroring