You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I’m trying to upgrade a project of mine to a newer set of dependencies, and I am encountering this build error:
Building library for aws-lambda-haskell-runtime-4.1.1..
[ 1 of 17] Compiling Aws.Lambda.Runtime.API.Version
[ 2 of 17] Compiling Aws.Lambda.Runtime.API.Endpoints
[ 3 of 17] Compiling Aws.Lambda.Runtime.Error
[ 4 of 17] Compiling Aws.Lambda.Runtime.Environment
[ 5 of 17] Compiling Aws.Lambda.Runtime.ApiInfo
[ 6 of 17] Compiling Aws.Lambda.Runtime.Context
[ 7 of 17] Compiling Aws.Lambda.Runtime.StandaloneLambda.Types
[ 8 of 17] Compiling Aws.Lambda.Utilities
[ 9 of 17] Compiling Aws.Lambda.Runtime.APIGateway.Types
src/Aws/Lambda/Runtime/APIGateway/Types.hs:216:31: error:
• Couldn't match expected type ‘T.Key’ with actual type ‘Text’
• In the first argument of ‘(.=)’, namely ‘k’
In the expression: k .= v
In an equation for ‘headerToPair’:
headerToPair (cibyte, bstr)
= k .= v
where
k = (T.decodeUtf8 . CI.original) cibyte
v = T.decodeUtf8 bstr
|
216 | headerToPair (cibyte, bstr) = k .= v
| ^
This is building against aeson-2.0.3.0, so that’s probably the issue.
Any plans for aeson-2 compatibility?
The text was updated successfully, but these errors were encountered:
nomeata
changed the title
Couldn't match expected type ‘T.Key’ with actual type ‘Text’
Support aeson-2.0
Jun 11, 2022
nomeata
added a commit
to nomeata/aws-lambda-haskell-runtime
that referenced
this issue
Jun 11, 2022
I’m trying to upgrade a project of mine to a newer set of dependencies, and I am encountering this build error:
This is building against aeson-2.0.3.0, so that’s probably the issue.
Any plans for aeson-2 compatibility?
The text was updated successfully, but these errors were encountered: