Fix Schema JSON stringification of undefined - #6633
Conversation
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthrough
ChangesSchemaGetter JSON stringification
Estimated code review effort: 2 (Simple) | ~10 minutes 🚥 Pre-merge checks | ✅ 2✅ Passed checks (2 passed)
Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@packages/effect/test/schema/SchemaGetter.test.ts`:
- Around line 18-23: Update the stringifyJson failure test around
SchemaGetter.stringifyJson to inspect the error returned by Effect.flip,
asserting that its _tag is SchemaIssue.InvalidValue and, if available in the
existing issue shape, that actual reflects the undefined value. Preserve the
test’s current input and effect execution while replacing the void-only
assertion with the contract-specific validation.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: CHILL
Plan: Pro Plus
Run ID: 9614a8f0-6d3b-412b-bbba-393b1937f635
📒 Files selected for processing (2)
packages/effect/src/SchemaGetter.tspackages/effect/test/schema/SchemaGetter.test.ts
Bundle Size Analysis
|
Summary by CodeRabbit
Bug Fixes
Tests
undefinedoutput) correctly produce anInvalidValueresult.