pathom

:pathom: https://github.com/wilkerlucio/pathom/ & https://pathom3.wsscode.com & https://roamresearch.com/#/app/wsscode
2020-06-04T13:30:56.174700Z

Mornin. Latest api pathom docs are working again https://github.com/cljdoc/cljdoc/issues/400. There's also a hidden rebuild button on cljdoc that Martin pointed out

Björn Ebbinghaus 2020-06-04T13:56:03.175700Z

Is there someone who had a problem with datahike not writing to its file when transacting inside a parallel parser?

wilkerlucio 2020-06-04T15:14:27.175900Z

nice! 😄

Thomas Moerman 2020-06-04T15:40:58.178700Z

Hi, newbie question: Imagine you have a mutation in which some complex context data structure must be checked first, is it an idiomatic approach to use the existing resolvers (e.g. via the parser) to query for the needed context using an EQL query? (hope this makes sense)

wilkerlucio 2020-06-05T13:14:17.179500Z

yes, that's totally possible, I remember writing a transform fn in the past that did just that

wilkerlucio 2020-06-05T13:14:22.179700Z

trying to find it here

wilkerlucio 2020-06-05T13:37:52.179900Z

couldn't find, but in a basic sense, you can just call the parser from inside the mutation (use the one from env, there is a :parser key there)

wilkerlucio 2020-06-04T15:42:25.178800Z

hello, you mean like, you have an input, then you use it compute more data, to then run the mutations, is like this?

Thomas Moerman 2020-06-04T16:06:52.179100Z

Yes. My idea was that I could perhaps leverage all the resolver logic that is already implemented to produce contextual data (needed in the mutation) in function of the mutation params and a graph query.

Thomas Moerman 2020-06-04T16:07:40.179300Z

then run some inspections on that data map to decide e.g. whether the mutation is allowed or not