Skip to content

docs: update schema validation use case to include Avro and Protobuf - #277

Merged
tombentley merged 1 commit into
kroxylicious:mainfrom
k-wall:issue-3826-schema-validation-multi-schema-types
Aug 7, 2026
Merged

docs: update schema validation use case to include Avro and Protobuf#277
tombentley merged 1 commit into
kroxylicious:mainfrom
k-wall:issue-3826-schema-validation-multi-schema-types

Conversation

@k-wall

@k-wall k-wall commented Jul 28, 2026

Copy link
Copy Markdown
Member

Summary

  • Remove the JSON Schema-only limitation (footnote) from the schema validation use case page
  • Update the schema validation description to list all three supported schema types: JSON Schema, Apache Avro and Protocol Buffers (Protobuf)

Fixes: kroxylicious/kroxylicious#3826

Test plan

  • Preview the site and verify the schema validation use case page renders correctly
  • Confirm the footnote restricting to JSON Schema only is removed
  • Confirm the supported schema types are listed in the description

🤖 Generated with Claude Code

Remove the JSON Schema-only limitation from the schema validation use
case page. The Record Validation filter now supports JSON Schema,
Apache Avro and Protocol Buffers (Protobuf) schema types.

Fixes: kroxylicious/kroxylicious#3826
Assisted-by: Claude Opus 4.6 <noreply@anthropic.com>
Signed-off-by: Keith Wall <kwall@apache.org>

@tombentley tombentley left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks @k-wall

@tombentley
tombentley merged commit eb2726a into kroxylicious:main Aug 7, 2026
2 checks passed
@github-project-automation github-project-automation Bot moved this from Blocked to Done in Release 0.24.0 Aug 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

docs(website): Update schema validation use case to remove JSON Schema-only limitation

2 participants