mullsork
Joined 13 years ago
Karma
212
Submissions
129
Member since
Jul 18
[ my public key: https://keybase.io/mull; my proof: https://keybase.io/mull/sigs/S8h4yTrZCar86_lwXf0HjhBjnjq57NojJGEOcMfmruc ]
View on Hacker NewsJoined 13 years ago
What? Who told you this?
For anyone curious.
Maybe you're not quite the average consumer that OP has in mind? Maybe you are, I don't know. Either way it's unsustainable and ridiculous that the _average consumer_ would need to replace something after 4 years when it COULD be built to last.
Looks like they do mean nix!
Result
.fromExecution(() => schema.parse(input))
.mapOk(parsed_input => /* */)
.mapError(parse_errors => /* */)
which is an alright way to deal with things IMO.I would hazard a guess that `parse` is a function introduced long ago, and `safeParse` came afterwards. (Safe as in "do not throw an exception")
Anyone using Hanami 2 in production that would care to share their experience?
edit: Postgres docs on MERGE: https://www.postgresql.org/docs/15/sql-merge.html