pathom

:pathom: https://github.com/wilkerlucio/pathom/ & https://pathom3.wsscode.com & https://roamresearch.com/#/app/wsscode
wilkerlucio 2021-03-07T00:18:52.060100Z

awesome! I think its a great way to understand how pathom works 🙂

wilkerlucio 2021-03-07T00:19:12.060300Z

I like ask you about this text on your docs:

one of the main differences from pathom is that pathos doesn’t bother about the code inside and you can easily use let and whatever your heart desires

wilkerlucio 2021-03-07T00:21:09.060500Z

not sure if I understand, because pathom doesn't care about the code inside the resolver, just what it outputs in the end, maybe a misunderstand of some sorts?

markaddleman 2021-03-07T16:53:24.063800Z

Should the resolver r be invoked in this example? Intuitively, I think it should.

wilkerlucio 2021-03-07T16:58:05.064100Z

the problem is that you are trying to override an already defined key :k, that wont work, once a value is set, pathom wont change it

wilkerlucio 2021-03-07T16:58:17.064300Z

you cant make a resolver to add information nested like that, not a thing

wilkerlucio 2021-03-07T16:59:00.064500Z

it probably is getting called, you just don't get the updated result (because :k was already set at that context)

markaddleman 2021-03-07T17:01:35.064800Z

Ah, ok. In fact, it is not getting called but no matter. Your explanation makes sense and, I should have realized that what was going on: It turns out that I rely on that behavior in other areas

markaddleman 2021-03-07T17:01:37.065Z

Thanks