From 6baf0b9ed0ce85a108390579ce873c956dd652f3 Mon Sep 17 00:00:00 2001 From: Michael Edelman Date: Fri, 12 Jul 2019 02:37:31 -0400 Subject: [PATCH] fix: correct typo in 'Idea #2' section (close#2513) (#2514) This change fixes a typo found on line 95 where the word 'wow' had been used instead of 'now' --- architecture/live-queries.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/architecture/live-queries.md b/architecture/live-queries.md index 68b8f467498..b8d8a3e9824 100644 --- a/architecture/live-queries.md +++ b/architecture/live-queries.md @@ -92,7 +92,7 @@ Incidentally, because we had started the engineering work behind Hasura many yea Because of implementing authorization at the application layer in Hasura (instead of using RLS and passing user-details via current session settings in the postgres connection) had significant benefits, which we’ll soon see. -To summarise, wow that authorization is declarative and available at a table, view or even a function (if the function returns SETOF) it is possible to create a single SQL query that has the authorization rules. +To summarise, now that authorization is declarative and available at a table, view or even a function (if the function returns SETOF) it is possible to create a single SQL query that has the authorization rules. GraphQL query → GraphQL AST → Internal AST with authorization rules → SQL AST → SQL