ticket.values description tells agents to use a 'formValues' field that does not exist
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- api
Research direction
Start in src/schemas/ticket.ts and inspect the TicketCreateSchema definition alongside the values description. Verify whether formValues is supported anywhere in the package, then update the schema or documentation so the published guidance matches accepted input and answers are not silently discarded. Use the reported dist/ searches to confirm the stale reference is gone or backed by a real field.
Written by the indexing model from the issue text.
Description
What happens
src/schemas/ticket.ts documents values as:
Raw form field answers keyed by field name (e.g.
{"dietary-needs": "Vegan"}). Agents using MCP should prefer passingformValues, which resolves field titles or IDs to field names automatically
There is no formValues field. It appears nowhere in the package except inside that sentence:
$ grep -rn "formValues" dist/ | wc -l
1
$ grep -rn "formValues:" dist/schemas/ | wc -l
0
Why it matters
The sentence is aimed specifically at MCP agents, and it is the kind of instruction a model follows literally. Because TicketCreateSchema is a plain z.object(), Zod strips unknown keys rather than rejecting them — so formValues is silently discarded, values is absent, and create returns success having dropped the attendee's form answers.
There is no error for a model to react to. The tool documentation actively steers callers into silent data loss, which is worse than having no description at all.
// what the description recommends
await Confetti.tickets.create(
{ eventId: 1, email: 'a@example.com', status: 'attending',
sendEmailConfirmation: false, formValues: { 'dietary-needs': 'Vegan' } },
{ apiKey },
)
// -> succeeds; the answers are gone
Suggested fix
Either implement formValues as described, or drop the sentence and document values alone. If it refers to something planned, it should not ship as advice in a released package.
Worth a wider check: this is the only description we found making a claim the schema does not back, but nothing currently prevents another.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- Avg merge
- 1h 51m
- Merged PRs (30d)
- 2
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from confetti/confetti-node
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
confetti/confetti-node#37 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
confetti/confetti-node#36 ·
-
Module-global yayson Store leaks records between requests (cross-tenant in multi-key processes) Open
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
confetti/confetti-node#34 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
confetti/confetti-node#38 ·
-
rate_limit_reached Open
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
confetti/confetti-node#17 ·
All issues in confetti/confetti-node
Similar issues
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 91/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100