Fork me on GitHub
Slack Archive

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

2022-08-25

Channels

#pathom
<
2022-08-25
>
Hukka05:08:36

I must be missing something. To my eyes, having either ab1 or ab2 would be sufficient, but both c1 and c2 would not be.

wilkerlucio05:08:46

man, I think you are right, that connection should be an OR :man-facepalming:

wilkerlucio12:08:04

I'm noticing its breaking to compile when I try locally, gonna check on it later

nivekuil14:08:20

I just realized there's paredit bindings (ctrl+right/left) in pathom-viz :O

😮 2
wilkerlucio15:08:55

its actually parinfer there 😉

pieterbreed15:08:32

What is the guidance for mutations that need ambient information? I have a system that up to now has only had resolvers. In the stack, the user-id was added to all inputs. Now that I created the first mutation I need that user-id too so that I know what user to perform the mutation against. What would be the recommended way to access this info? I can think of 1) add to the environment 2) add to the parameters (which would be awkward since the user-id is not known at the call-site) 3)??

wilkerlucio15:08:47

the common thing is to send as a param to the mutation from the client

1
wilkerlucio15:08:03

something like: (user/update {:user/id 1 :user/name "New Name"})

pieterbreed15:08:26

thank you. One last question. Are db connections inputs or do they belong to the environment?

sheluchin15:08:15

Typically you have connection information in your config, which you pass along in your environment.

1
donovanmcgillen18:08:08

Hi. I'm trying (and failing) to find an example of wrap-mutation-error. We use wrap-resolver-error to log and return a map (so we don't get transit marhsalling exceptions) whenever a resolver throws an exception (which shouldn't normally happen but it certainly does during development!), and I want to do the equivalent in mutations. The resolver one uses the supplied mark-node-error fn that it is given, but I'm unsure what I'm supposed to do with mutations. The plugin does get called because my logging is happening, but I'm still getting an exception telling me that the original exception couldn't be marhsalled because I'm not sure how to replace it with my error map. Any pointers? Thanks!

wilkerlucio00:08:17

hello, I did look and this entry point is broken, but easy thing to fix, I'm already doing some work on Pathom now, I can add that to the list

donovanmcgillen08:08:41

Nice one, thanks for that 👍

donovanmcgillen08:08:24

Oh I see you've literally already fixed it and made a release - what service! Working as expected for me now, many thanks for that

🙏 1