Repository navigation
SAAS-10250 - build-plugin: the platform now provides Ignore certificate errors - #143
Merged
Merged
Conversation
SquaredUp now adds the toggle to every WebAPI-based plugin, so new plugins shouldn't declare their own field. Document the base.config literal as the opt-out. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
🧩 Plugin PR Summaryℹ️ No plugins were modified in this PR. |
Contributor
andrewmumblebee
approved these changes
Oct 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
📋 Summary
This PR updates the
build-pluginskill so it stops telling authors to add their ownignoreCertificateErrorscheckbox to ui.json. SquaredUp now adds an "Ignore certificate errors" toggle to every plugin built on WebAPI (SAAS-10250), so new plugins don't need the field, or abase.configmapping for it.The skill also explains that declaring the field, or setting the key in
base.config, stops the platform adding its toggle. That's only worth doing for an API where the option makes no sense, and it only hides the option on the form.Important
Please don't merge until the SAAS-10250 platform change is in prod. Before then, a plugin built with this guidance would ship with no option at all.
Existing plugins that already declare the field don't need to change. The platform skips them.
🔍 Scope of change
📚 Checklist
🤖 Generated with Claude Code
Summary by CodeRabbit