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?

@U066U8JQJ the most annoying thing I encounter when using pathom is having to write in such a way that the first element in resolver is a map

in pathos I use a simple macro that goes as far into the function as possible, assuming that the last element returned by the function is either a map or a keyword

this was the first thing that caught my eye as I read the pathom3 documentation

@U066U8JQJ i created a PR, maybe you will find it useful

another thing that I don't think pathom makes easy is memoization with ttl, and I think it would be super useful. sometimes data changes every certain time and it would be a good idea to only retrieve it when it's changed

and by the way, thanks not even for a piece of really great software that I use every day, but for changing my perspective on programming and specifically data driven development ❤️

i take back what i said about memoization, last time I looked in the documentation, i didn't see the section about cache

hello Ribelo, I posted the reasoning for not having deep checks for output in your issue

about cache with TTL, the cache system in Pathom 3 is made to be extensible, you can use the TTL from core.cached for example, there is some integration examples at https://pathom3.wsscode.com/docs/cache

thanks for the feedback, always appreciated

I read an explanation of why deep check is not a good idea and well, you are right. I hadn't thought of that. 😉