Echo JS 0.11.0

<~>
pinceladasdaweb 27 days ago. link parent 1 point
That "I don't quite trust it yet" feeling is exactly where I lived for two years — and what fixed it for me wasn't more coverage, it was one specific kind of test: kill the dependency for real, from the server side, while the library is mid-work, and assert full recovery. For Redis that was CLIENT KILL; for an MS-SQL client I'd bet the bodies are buried around killing the connection mid-transaction. My "pretty thorough" functional tests kept passing while reconnection had literally never worked once.

Two things that let me ship anyway: making the README document what the library does NOT do (mine says the lock is single-instance and not Redlock, in bold — honesty is cheaper than a support ticket), and doing the scary refactors only AFTER the destructive suite existed. So your pending transactions refactor might actually be an argument for writing those tests now, not for delaying the release.

The query ergonomics doc looks genuinely nice. FWIW, "bulletproof before people rely on it" never arrives — other people's workloads are the one test suite you can't write yourself.

Replies