Ramnivas Laddad

Currently, all filters define predicates where one operand is a column and other a literal. We should support cases where both operands are columns. For a concrete example, see https://pgexercises.com/questions/basic/where2.html

Currently, AuthContext must be expressed as follows: ``` context AuthContext { id: Int @jwt("sub") role: String @jwt("role") } ``` It will be better if we could express "sub" and "role"...

Since our language is growing, we should implement a Language Server Protocol so that we can offer code completion, jump to definition, error reporting, linting etc. We may also offer...

Not all data can come from just the db. Therefore we need to support integration with REST and other GraphQL services. This requires: - [ ] Support for declaring remote...

Support arrrays and objects database columns

1

In addition to the standard primitive we support, we need to support array and object database columns). These would be treated as "primitive" from a certain perspective (specifically, no relation...

Improve support for primitive types

1

Currently we supports only Int and String types (and with not so valid operators for String). - [ ] Expand support for all common database types - [x] #90 -...

Currently, the WASM plugin doesn't support any access control (it allows specifying the `@access` annotation, but ignores it while resolving). While doing so, we should try to abstract access solvers....

Revisit how we use primitives in the context of the new plugin system

1

Currently, we enforce a set of plugins onto each plugin. This allows us to have a common definition of types such as `Int` and `Float`, but it also means each...

Protect environment variable from being accessed by non-privileged code

1

We have a good differentiation between `Exo` and `ExoPriv`--the former can operate only at the calling request's context. This simplifies reviewing code: if it is just `Exo`, rest assured that...

With the change in the design where all types--except primitives and context--belong to each service, we have a bit of unclear code in typechecker. Specifically, we have all types from...