pathom 2021-08-05 | Slack Archive

Is it possible to configure a resolver in pathom2 so it never stores its results in request-cache ?

::pc/cache? false on the resolver configuration

awesome! thanks 🎉

Started the migration from a custom store api (based on https://github.com/cyppan/grape) to Pathom 3, with batching and async, and look at the number of opened connections to Mongo already... 😄

🎉 14

Pragyan Tripathi08:08:43

Wow… this makes me sure I should try it out in my own project..

👍 2

nivekuil20:08:48

bug report: process-one will NPE if the attribute it gets back is nil, because of val

👀 3

wilkerlucio13:08:44

can't reproduce, do you have an example?

nivekuil20:08:56

well, it happens if process returns {} so it tries to call (val (first {}))

nivekuil20:08:14

so all you have to do is ask for attribute that isn't in the index (with lenient on)

wilkerlucio21:08:47

I tried an example but I didnt see the error, a broken example really helps so I dont have to assume anything (like lenient mode)

nivekuil00:08:38

huh, that's harder to repro than I thought. I figured it would be an easy fix since process can return empty map (according to its spec too), in which case you can see that it will always NPE

nivekuil00:08:35

e.g. (peek (first instead of (val (first

2021-08-05

Channels