From 86b74b160f0d6eb1d9020ff70f1f455d592d303c Mon Sep 17 00:00:00 2001 From: Fabiano Taioli Date: Tue, 20 Oct 2020 14:51:15 +0200 Subject: [PATCH] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 41315f1..707d61d 100644 --- a/README.md +++ b/README.md @@ -56,7 +56,7 @@ Some aspects of Knex I like less: * **Mutable**. Every time you specialize in your query calling some method (.where, .limit, .join, etc.) you are mutating the same instance. This makes it harder to compose your apps. -* **Not Lazy**. Being based on Promise, the query is materially executed the moment you call .then on the builder or try to "await" for the result. You cannot composer your program in a Pure way leaving the actual "impure" query execution as the last step. +* **Not Lazy**. Being based on Promise, the query is materially executed the moment you call .resolve on the builder or try to "await" for the result. You cannot composer your program in a Pure way leaving the actual "impure" query execution as the last step. So, let's introduce you IODIO. It's a monadic wrapper of a Knex query builder and a Fluture Future that represents the result of the query. It's lazy and pure, so you can program in advance your computations (query composition and/or result transformation) and run all as the last step.