#Erik Sipsma3294 Another thread in one
drowsy dragon
The name of the resolver to call is included w/ the payload.
The hacky implementation is here: https://github.com/dagger/cloak/blob/dbc0fbe1a5084ac4cf52b7587f19c6a33eedacd1/api/graphql.go#L184
Can be made more robust. If we decide to handle subresolvers in the future then it will also need some updates of course too, but the same basic idea should still hold
glacial kindle
There's the case of invoking "deploy" on netlify, easy enough
There's the hypotehtical case of invoking "netlify" on netlify, which itself has a "deploy" -- not sure here
There's the hypothetical case where netlify could extend Filesystem, in which case we'd need to invoke the nested deploy somehow -- not sure here either
I see -- so we'd need some kind of path encoding between the two
drowsy dragon
I see -- so we'd need some kind of path encoding between the two
Yes, will be part of the protocol
glacial kindle
ok ok
drowsy dragon
Btw, very close to finishing up that branch to a just mergeable enough state, just have one more existing action to convert over to the new model. The chaining+caching is working though, pretty cool
glacial kindle
Nice!
Wasted a bunch of time for personal reasons today, didn't make as much progress as I wanted
Which resulted in postponing my trip to EU, so on the bright side we'll still be on the same time zone next week
drowsy dragon
Oh shit that sucks! Are you still going there, just at a later date?
But yeah no worries at all, I am not blocked in the slightest by anything