Ramnivas Laddad
Ramnivas Laddad
This is a follow-up from @affanshahid's comment in #1000 and his https://github.com/affanshahid/exograph-deno-utils repository. At a high-level, `exograph-deno-utils` does the following: 1. Walks through the user code and generates gql.ts file...
Consider https://github.com/exograph/exograph/blob/0bc417eed9a506c7b7ab51535e908bb70c88774f/integration-tests/embedding/deno/src/index.exo#L23. Here is the intention it to pass along the selection to the underlying query (in other words, except for translating the `searchString` to its embedding, nothing should change)....
Moving @shiftlabs1's comment from #907 (since the original issue of createdAt/updatedAt is now resolved) I think if triggers can be "attributified", that will be nice . for e.g if i...
Earlier we relied on web framework-specific mechanism to implement CORS. Specifically, we used actix-cors, which of course won't work elsewhere (such as Cloudflare Worker). In this PR, we implement CORS...
For example, we don't support Deno in Cloudflare Worker deployments. So, `exo deploy cf-worker` should error if the `exo` file has a `@deno` section. Implementation notes: We keep the names...
If a ts file has an error, it produces no meaningful error. Instead, it just crashes with: ``` thread 'main' panicked at crates/deno-subsystem/deno-model-builder/src/system_builder.rs:238:6: called `Result::unwrap()` on an `Err` value: Any...
Currently, there is an RC for Deno.