pathom

:pathom: https://github.com/wilkerlucio/pathom/ & https://pathom3.wsscode.com & https://roamresearch.com/#/app/wsscode
wilkerlucio 2021-02-14T03:59:06.258Z

hello, I wanna think a bit more about it maybe there is a different extension point for it., but I would suggest to not mix smart maps with in resolvers, you should try to just make the resolver ask for the most direct input you need, and can you always add more resolvers to the game, doing smart maps inside resolvers will make your runs more unpredictable and harder to debug (and probably running slower, given you have to plan more times than if you delegated to pathom to do in a single go)

wilkerlucio 2021-02-14T04:00:29.258300Z

and putting a smart map on an entity is a bad way to do it, because then you add smart map overhead to each and every operation that pathom does (and that can be a lot of merges)

wilkerlucio 2021-02-14T04:08:59.258500Z

all that disclaimer said, to make it "work", the wrapper would need to be in another place, write now it kinda of go around the "node execution", the resolver itself is a bit more inner, so I'm considering if I should rename the current to something like ::pcr/wrap-run-node, and use the ::pcr/wrap-resolve to run around the actual resolve, this could allow for a more internal manipulation of what goes in the resolver, and what goes out

wilkerlucio 2021-02-14T04:09:11.258700Z

would be a breaking change, but I'm still open for that at this stage