awesome! I think its a great way to understand how pathom works 🙂
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
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?
Should the resolver r
be invoked in this example? Intuitively, I think it should.
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
you cant make a resolver to add information nested like that, not a thing
it probably is getting called, you just don't get the updated result (because :k
was already set at that context)
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
Thanks