Repository navigation
feat: set up check-in for a form from the command line - #52
Merged
Merged
Conversation
kba977
force-pushed
the
feat/checkin-campaigns
branch
2 times, most recently
from
October 16, 2026 07:23
9935738 to
9692652
Compare
Check-in is one of the most used plugins, and setting it up meant going through the web app. The checkin commands cover the whole campaign. - checkin list/get/create/edit/delete call the check-in campaign operations of API v1 - create takes the form, the check-in and display fields, whether to show a check-in code, and whether to make the check-in field required and unique; times and a location limit go through --json - edit pauses and resumes with --disable and --enable, like opensearch edit - delete asks for --yes, like every other delete - checkin --help walks through using it with a form spec/openapi.yaml is refreshed from the published spec, which now has the check-in operations; it also brings the field settings and goods item schemas the API added since the last sync. The account needs the check-in plugin enabled. Refs: #T17519 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
kba977
force-pushed
the
feat/checkin-campaigns
branch
from
October 16, 2026 07:24
9692652 to
c054b6d
Compare
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
1 participant
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.
Why
Check-in is one of the most used plugins, and setting it up meant going through the web app. These commands let a script or an agent set up and manage a check-in campaign for a form.
What changed
checkinresource:list,get,create,edit,delete, against/api/v1/plugins/checkin/campaignscheckin create --form <token>takes the check-in field (default: the first mobile field, then the first name field), the field shown when verifying,--no-check-in-code, and--unique-check-in-field; times and a location limit go through--jsoncheckin editpauses and resumes with--disable/--enable, likeopensearch editcheckin deleteasks for--yes, like every other deleteNotes
Needs a backend that serves the new plugin endpoints, and the account needs the check-in plugin enabled. Only the campaigns the caller created are listed or editable.
Tests
npm test(270 pass) andnpm run check.🤖 Generated with Claude Code