This separate executable spits out the list of dependencies for a stack-based project. We should have similar functionality in the web interface. I'm not sure exactly how to do it...
Separate endpoint, or allow dependencies on / to be optional replaced with this behavior
The latter is nice, but do we have to make it no longer a GET if we're going to post the configuration files required to compute dependencies?
Should the client POST package.yaml files or x.cabal files?
The former is far easier to parse, but then you're tied to hpack.
This separate executable spits out the list of dependencies for a stack-based project. We should have similar functionality in the web interface. I'm not sure exactly how to do it...
Separate endpoint, or allow
dependencieson/to be optional replaced with this behaviorThe latter is nice, but do we have to make it no longer a GET if we're going to post the configuration files required to compute dependencies?
Should the client POST
package.yamlfiles orx.cabalfiles?The former is far easier to parse, but then you're tied to hpack.