Closed jhrcek closed 3 years ago
The fix might be even simpler than that.
runRequest
was un-exposed from Servant.Client.Core
starting from servant-client-core 0.18.1
.
I looked at exact version differences between servant client and the way to fix this could be to import runRequest
from Servant.Client.Core.RunClient
which is the module that all servant versions from 0.16 onwards as illustrated by following gif:
Closed by @jhrcek in #20.
Hello @cdepillabout . Could you please release the version with this fix to hackage? This would simplify our project's stack config (depending on package from hackage is arguably simpler than depending on specific commit in 3rd party repo).
@jhrcek I think this version should be on Hackage?
https://hackage.haskell.org/package/servant-rawm-client-1.0.0.2
Are you having trouble using this version?
Sorry, turns out it was my mistake. We had servant-rawm dependency declared in cabal since before the package was split into client/server subpackages. Removing that and adding extra-deps for these 2 new packages to stack.yaml fixed the issue.
I'm building an application with stack lts-17.6 This lts contains
servant-client-core
version 0.18.2 (https://www.stackage.org/lts-17.6/package/servant-client-core-0.18.2)Unfortunately
servant-rawm-client
doesn't work with this version ofservant-client-core
. I'm getting the following compiler errorIt seems things have been moved around in newer versions of servant-client and
runRequest
now lives in Servant.Client.Core.RunClient.Would you accept a PR with CPP-based fix for this?