Juan Manuel Verges

Hey @natew has there been any work on this, I'm actually in need of this feature. I need it to consume [Dgraph graphql](https://dgraph.io/docs/graphql) API, they have a [cascade](https://dgraph.io/docs/graphql/queries/cascade) directive that...

@vicary I like the first and third ideas, the second one will complicate things, since then `query.url` type is a `string | function`, when using it the developer will have...

The first one, has less code between the two, for the case of `no-unused-vars`, we could have the proxy trap for the `$directives` to only accept functions with optional arguments,...

Indeed, when having that in mind, it's not trivial. What about a function like the one proposed by @natew in the first comment? ```js directives(query.queryPost.title, [ { foo: { ttl:...

@benjie I'm in need of this feature, particularly the third case of the multitenancy options listed by @bozada. I'm considering tackling this, could you give some insight as to how...

I forgot to mention, that my particular use case, depends on values from the http request to set the postgres `search_path` in order to select the respective schema to query...

@bostontrader not sure if you are still interested, but this might help https://github.com/prisma/quaint

Why not delegate the custom validation processing to each property FormControl and have Angular handle it?

I'm also curious about the "consideration behind the model part". I've been using this package and its awesome, but can't avoid questioning the reasoning behind the model part, I would...

I'm having exact same problem with a newly created starter basic app, no changes, just adding the adapter as described in the cloud-run deployment section in the docs. If I...