https://pathom3.wsscode.com/docs/resolvers/#priority-number

thanks, didn't know about priorities, the issue here though is that both chains are starting with the same resolver

hello Eric, yes, you right, without the weight tracker, Pathom by default will only try to prioritize via explicit declarations, but I see the point in your case, when some options start the same, kinda makes sense that the smaller should go first

that said, are you using latest pathom version? and have you tried turning on the experimental path optimizations? I think in your case there, if you turn them on, you might not have these duplicated subpaths

please let me know if you have a chance to try it, wonder if will affect your planning tree

(to enable experimental optimizations, add to your env: :com.wsscode.pathom3.connect.planner/experimental-branch-optimizations true)

@U066U8JQJ this is with both optim and weight plugin (graph and chosen path are the same without optim)

optim alone is taking a longer path (and the graph is exactly the same as no optim/no weight plugin)

looking at the source provides is the output converted by a function called query->shape-descriptor which Convert pathom output format into shape descriptor format

`Shape descriptor is a format to describe data. This format optimizes for fast detection of value present given a shape and a value path.`

Ok - guess I feel somewhat better then. That's not too far from the comment I made on that s.o. question. Thank you for the check!

yeah, all good, just add my entry there, hope it can still helps 🙂