Skip to content

Support literal/union types in pipe parameter validators #134

@gnzjgo

Description

@gnzjgo

Description

Currently pipe parameter validators (p.string(), etc.) don't support constraining values to a set of allowed literals (union/literal types).

This would be useful for parameters like sort order or filter modes where only specific values are valid.

Example

params: {
  order: p.string().literals('asc', 'desc'),  // type: 'asc' | 'desc'
  status: p.string().literals('active', 'inactive', 'pending'),
}

This would provide both TypeScript type safety and runtime validation.

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