© 2026 Hedgehog Software, LLC
Twitter
GitHub
Discord
System
Light
Dark
More
Communities
Docs
About
Terms
Privacy
Search
Star
Feedback
Setup for Free
Using `Schema.optionalToRequired` to Throw `ParseError` Instead of Default Value - Effect Community
EC
Effect Community
•
6mo ago
tyko
Using `Schema.optionalToRequired` to Throw `ParseError` Instead of Default Value
Is there a way to use
Schema.optionalToRequired
Schema.optionalToRequired
where I can throw a
ParseError
ParseError
instead of providing a default value on decode
?
Effect Community
Join
Production-grade applications in TypeScript.
6,221
Members
View on Discord
Resources
ModelContextProtocol
ModelContextProtocol
MCP Server
Recent Announcements
Similar Threads
Was this page helpful?
Yes
No
Similar Threads
Can `ParseError` Extend `Schema.TaggedError` Instead of `Data.TaggedError`?
EC
Effect Community / schema
2y ago
Proposal to Change `ParseError` to `Schema.TaggedError`
EC
Effect Community / schema
3y ago
Equivalent Schema.Config Usage for Default Value
EC
Effect Community / schema
4mo ago
Compatibility Issue: Extending `ParseResult.ParseError` to `Schema.All` for `Schema.TaggedRequest...
EC
Effect Community / schema
2y ago