Ramnivas Laddad
Ramnivas Laddad
Consider `lt_values`, `gt_values` etc in `core_resolver::access_resolver`. Currently, it assumes the values to be numbers. We need to consider other types. For example, we should be able to compare timestamps, dates,...
Currently, `@access(false)` (and its versions, such as `@access(query=..., mutation=false)` mean the API is available but not usable by anyone. Another possible interpretation is to remove the API from our schema...
Currently, `Exograph` can perform both queries and mutations. Like `ExographPriv`, it may help if we offer limited version of it to perform only queries. This may help with #32, since...
This is an umbrella issue, so when we start fixing it, we should open specific new issues and fix those. Currently, we have `unwrap()`s and explicit `panic`s in several places....
See `InsertTransformer`. When we get nested insertions, we produce a SQL statement, we produce a CTE with parameters proportional to the length of the nested elements. Instead, we should produce...
Consider Concert -> [ConcertArtist]
Currently, both side of a relationship need to refer to the other side. However, this can be an issue when using (for example) an independently developed exo model. We can...
Currently, we support access rules for query, create, update, and delete. However, they apply to both forms of APIs: single and bulk. We could offer a more fine-grained control. Along...
Currently, we create shallow objects initially and later expand them. We should add an assertion that none of the objects in any arena remain shallow.
Currently, we use `@column` to designate both: the column in the current table and the column in the foreign table (inferred based on the cardinality), but this can be confusing....