Isaac Whitfield

I agree this should be better documented. I am against runtime errors as above... I think? I'm wondering if we simply make the requirement that routers only work on binary...

I am going to assign this to the 5.x milestone, so that we can handle this with potential breaking changes as necessary. I do think there are improvements we can...

@alexhendel just curious if you ever resolved this on your side? We're using Nexus and facing the same thing. Works with legacy builder, just not BuildKit.

Hi @chevinbrown! I think I might be missing something. Why can't you just use `Cachex.fetch/4` and avoid the wrapper? Why does it specifically have to be `Cachex.get/3`?

Based on what you've said, `Cachex.fetch/4` is the thing to use - it's exactly for what you're describing! > Every Cachex.fetch will have to implement a database-lookup as fallback to...

> yes, but with one augmentation. fetch/4 would require implementing the fallback at every callsite. This would make sense, but you're already using a function reference and a wrapper. How...

Ah, okay, that totally makes sense -- thank you for your patience @chevinbrown! Yeah, the documentation seems a little lacking on the `type/0` pattern, I'm not sure when that happened...

Yeah, this is a known thing I am still trying to figure out. The issue is that we purge directly via an ETS query, and so it's not actually possible...

Those are both equivalent, right? It's just that within your app you are using atom keys for maps, and when you read back from the database you are using binary...

Hi @chevinbrown! No problem, I'm sure we can figure it out. This is really hard to answer without actually looking at the code, but it sounds like we're going down...