Stephen Haberman
Stephen Haberman
I.e. ``` author.books.load({ where: ..., orderBy: ... }) ``` Would probably turn into: ``` em.find(Book, { where, orderBy }); ``` Although we could probably do better auto-batching b/c we know...
Right now we can do `idType: "untagged-string"` to get `author1.id` to be `"1"`, but don't support returning `1` an actual number.
As a full knex replacement: https://www.jakso.me/blog/kysely-a-type-safe-sql-query-builder-for-typescript
Currently reactive validation rules are always ran on create, to facilitate rules like: ``` config.addRule("lineItems", (c) => { if (c.lineItems.get.length === 0) { return "Must have at least one line...
Currently `skipIf` and `postClone` implementations need to use `instanceof` quite a bit: ``` const clone = await ctx.em.clone(original, { deep: { itemTemplates: "items", items: {} }, skipIf: (entity) => entity...
We currently have a `beforeDelete` rule that is not working correctly: ``` config.beforeDelete(["commitment"], async (cli) => { const commitment = cli.commitment.get; if (commitment) { if (!commitment.canBeEdited) { throw new Error("Cannot...
Currently `ValidationError` has entity-level knowledge of what caused an error: ``` export type ValidationError = { entity: Entity } & GenericError; ``` But it doesn't have field-level knowledge. Ideally this...
Right now `load` methods take a `forceReload` param, that is used by `em.refresh` to tell the various collections/references to invalidate their local state and re-issue queries to the dataloader layer....
I.e. auto-upload the latest schema / something like that https://dbdiagram.io/home
- Loading - Production code path should never load the env - Tests need to load the env from Webstorm/vscode, done in `setupTests`? - Could use `setupTestEnv.js`, set `process.env.STAGE=local` and...