From Discord: Exploring the possibility of making partial behave like optional with exactness

[effect-bot]

Summary

The user is trying to update from version 0.53.1 to 0.62.5 of a library and is wondering if it is possible to make the partial behavior similar to the optional behavior. They noticed that the optional type adds undefined to the schema by default and has an option to be exact, but the partial type seems to always behave as if the { exact: true } option is passed in.

Key takeaways:

• The user wants to explore the possibility of making partial behave like optional with exactness.
• The user is updating from version 0.53.1 to 0.62.5 of a library.
• The optional type adds undefined to the schema by default and has an option for exactness.
• The partial type seems to always behave as if the { exact: true } option is passed in.

Discord thread

https://discord.com/channels/795981131316985866/1206920245898518588