Paris Holley
Paris Holley
@dbushong 1. I suppose if your goal is adhere to async.js API and not introduce the niceties of promises, sure, but it is a pretty harmless change. 2. I do...
@dbushong Yes, but if I want to execute items in series, I have nothing :) Readme updated
i made a attempt at extracting the fluent'ness but ran into some typing issues.. though it may be possible with right magic. also realizing as i go that my scope...
in retrospect, i don't remember why i actually needed to downgrade anymore.. any validation callbacks should be listening to the state via get() incase of changes... took it out and...
Interesting thing to note, this behavior seems to be related to the fact that the class property names are different. In the example above, the `passiveId` is not inserted into...
i'm not sure what the implications are w/r/t propagation and other internals, but as far as fixing my insertion issues, it just requires some de-dupe work inside here: https://github.com/mikro-orm/mikro-orm/blob/f0cbcc2d977ffb8b867a21ee2ac857ef26986d73/packages/knex/src/AbstractSqlDriver.ts#L243-L274 i...
> This could work only if you handle contexts yourself not necessarily, java world introduces this concept via decorators as well (eg: spring's @Transactional(readOnly=true). I assume that the RequestContext could...
yep, qb would be limited to select, count, etc
Use Case: I have a invoice modification service, where I pass in a partial invoice line and I want the service to either: * If the line amount = 0...
> for me it's not even the suggested way, I do suggest using constructors directly every time I can i started using `em.create`/`em.assign` mostly because it was more ergonomic to...