Skip to content

RSVP status accepts values outside the allowed enum #116

@MajorTal

Description

@MajorTal

Summary

rsvps.setStatus persists arbitrary RSVP status strings. Live QA submitted status: "not-a-real-rsvp-status"; the capability returned success and stored that value.

Expected

RSVP status should be limited to the supported values: going, maybe, and cancelled. Invalid values should return a validation error and leave the current RSVP unchanged.

Evidence

  • Live target: https://eagles.kychon.com
  • Temporary QA data was cleaned up after the repro.
  • Spec: openspec/specs/events/spec.md:23 defines the allowed RSVP statuses.
  • Handler area: functions/kychon-api.js:1092 and functions/kychon-api.js:1115 write input.status || "going" without enum validation.

Suggested Test

Add tests for create and update paths that reject unknown RSVP statuses, empty strings that should not silently coerce, and casing variants such as Going.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions