Currently, stack is using the manually modified ssm.cabal to construct the build plan. This is not an immediate issue, but it is a bit concerning that stack.yaml and the generated ssm.cabal have now drifted apart. In particular, stack.yaml still points to the src/ directory, which contains some unused code.
The easiest thing to do is just to delete ssm.cabal; stack still works without. We can also consider committing to stack entirely; not having to declare exposed-modules and having stack infer them is nice, but not a must-have.
Currently, stack is using the manually modified
ssm.cabal
to construct the build plan. This is not an immediate issue, but it is a bit concerning thatstack.yaml
and the generatedssm.cabal
have now drifted apart. In particular,stack.yaml
still points to thesrc/
directory, which contains some unused code.The easiest thing to do is just to delete
ssm.cabal
; stack still works without. We can also consider committing to stack entirely; not having to declareexposed-modules
and having stack infer them is nice, but not a must-have.