[Cases] Re-implement runtime types in zod#258427
Merged
Merged
Conversation
lgestc
added
release_note:skip
Contributor
|
Pinging @elastic/kibana-cases (Team:Cases) |
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
lgestc
changed the title
Contributor
christineweng
left a comment
christineweng
left a comment
There was a problem hiding this comment.
@lgestc Appreciate you taking this on! Overall LGTM, left some comments on attachment V2 coverage
christineweng
approved these changes
Apr 1, 2026
Contributor
💚 Build Succeeded
Metrics [docs]Unknown metric groupsReferences to deprecated APIs
Unreferenced deprecated APIs
History
|
Contributor
|
@lgestc Have you considered reusing the types from |
Contributor
Author
looking into it:) thanks! |
Contributor
💚 Build Succeeded
Metrics [docs]Unknown metric groupsReferences to deprecated APIs
Unreferenced deprecated APIs
History
|
ersin-erdal
pushed a commit
to ersin-erdal/kibana
that referenced
this pull request
May 6, 2026
## Summary This is stage 1 of the migration, see [[Epic] [Cases] Migrate away from io-ts](elastic/security-team#16437) This implements all io-ts types as zod schemas; a stepping stone towards full migration None of the types are used for validation yet, they will be enforced in future PR's that will follow this one. ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ... --------- Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This is stage 1 of the migration, see [Epic] [Cases] Migrate away from io-ts
This implements all io-ts types as zod schemas; a stepping stone towards full migration
None of the types are used for validation yet, they will be enforced in future PR's that will follow this one.
Checklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.
Identify risks
Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss.
Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging.