pathom

Tom H. 2024-01-30T08:12:49.705019Z

When getting an attribute-unreachable error, is there a way to find out why it was unreachable? For instance, I might have a resolver that needs :a and :b to resolve :a+b , I have :b but not :a, is there a way I could ask Pathom (or use the indexes directly) to tell me I need :a specifically?

wilkerlucio 2024-02-01T17:56:27.076249Z

hello Tom, sorry the delay, I remember I do provide something for that in the run stats (from the meta) but I don't remember exactly, I can look for you but I need to find some time to stop and do some experimenting here to find it out

Tom H. 2024-01-31T04:32:06.979199Z

Inspecting the metadata on the params passed to :a+b , specifically :com.wsscode.pathom3.connect.planner/available-data has been handy so far

Tom H. 2024-01-31T04:33:07.600029Z

but I needed to make all of the inputs optional for it to get that far

Tom H. 2024-02-07T11:17:55.664489Z

All good! I'll keep exploring the metadata

Tom H. 2024-01-30T08:14:08.827679Z

Also the documentation for :com.wsscode.pathom3.error/attribute-unreachable appears to be missing/broken on the website: https://pathom3.wsscode.com/docs/error-handling/#attribute-unreachable

wilkerlucio 2024-02-01T17:56:39.608779Z

thanks, I will double check it

❤️ 1
Tom H. 2024-01-30T08:16:22.989889Z

as well as the “Types of attribute errors” diagram https://pathom3.wsscode.com/docs/error-handling/#types-of-attribute-errors