Benjamin Pannell

Hi @mikeroth7, thanks for reminding me about this. It just clicked for me that you're using `Model.update()` to do your upsert operations, so I assume your code looks something like...

Hi @CatGuardian, This was something I did consider when creating Iridium, however I opted for the explicit approach for a number of reasons. Most notably, people tend to be bad...

Hey @acuntex, this sounds really odd. There isn't any caching in place at all (unless you've implemented a caching plugin), so there shouldn't be any strange interactions. To me more...

Hi @louy, You're not wrong, however you should be aware that hooks are intentionally incapable of performing blocking async operations (a heavy handed way of preventing people from adversely affecting...

Back onto this topic, adding a core parameter is probably the cleanest approach - but it does represent a change to the external API (so in other words, major version...

Coming back to this following #22 - the use case you're referring to here is very much a relational one. While there are undoubtedly situations in which you need to...

Unfortunately that is the case, the best solution is (if you're happy to work with a singleton) to move the model (which has a reference to core) into the static...

While I can certainly see where you're going with that, the official recommendation also clearly states that: > Generally in MongoDB, you would not use an auto-increment pattern for the...

Hi Dmytro, I'm sorry that you've bumped into this issue, it's caused by v2.4 of TypeScript if I remember right and has been addressed on the `v8.x` release branch (which...

Hi @CatGuardian, Thanks for the really well documented feature request, it's definitely something that has stood out as a sore point in using Iridium ever since the initial transform framework...