Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support OpenAPI and AsyncAPI validation cases #814

Closed
jfallows opened this issue Feb 27, 2024 · 0 comments · Fixed by #875, #873 or #830
Closed

Support OpenAPI and AsyncAPI validation cases #814

jfallows opened this issue Feb 27, 2024 · 0 comments · Fixed by #875, #873 or #830
Assignees
Labels
story Feature description from user's perspective

Comments

@jfallows
Copy link
Contributor

jfallows commented Feb 27, 2024

Describe the desired outcome from the user's perspective
As an API consumer, I want to define OpenAPI validation behavior of zilla using the corresponding OpenAPI specification document for the HTTP API.

Acceptance criteria

  • integer validation (text or binary)
    • int32, int64
    • max and min value
    • multiple of N
  • number validation (text or binary)
    • float, double
    • max and min
    • multiple of N
  • string validation
    • max and min length
    • regular expressions

Additional context
Review any remaining validation syntax in OpenAPI for enforcement via zilla model validation.

@jfallows jfallows added the story Feature description from user's perspective label Feb 27, 2024
@jfallows jfallows changed the title Support OpenAPI validation cases Support OpenAPI and AsyncAPI validation cases Mar 13, 2024
@jfallows jfallows closed this as completed Apr 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment