You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Because we're dealing with the wild and wacky world of file metadata, there might be situations where data comes back in ways we don't expect and probably do not want. (I'm looking at you, PDF headers...) We've tried using dry-validation and dry-struct from the dry-rb gem family, but they have some quirks that outweigh their benefits - namely situations where things that are set to be optional turn out to be strictly enforced.
We could just simply type-check everything that comes through when we save it, or use something like https://github.com/julik/mal, or return very very large structs with lots of nils... or something else entirely.
The text was updated successfully, but these errors were encountered:
Because we're dealing with the wild and wacky world of file metadata, there might be situations where data comes back in ways we don't expect and probably do not want. (I'm looking at you, PDF headers...) We've tried using dry-validation and dry-struct from the dry-rb gem family, but they have some quirks that outweigh their benefits - namely situations where things that are set to be optional turn out to be strictly enforced.
We could just simply type-check everything that comes through when we save it, or use something like https://github.com/julik/mal, or return very very large structs with lots of nils... or something else entirely.
The text was updated successfully, but these errors were encountered: