Skip to content

Support aeson-2.0 #120

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
nomeata opened this issue Jun 11, 2022 · 1 comment
Closed

Support aeson-2.0 #120

nomeata opened this issue Jun 11, 2022 · 1 comment

Comments

@nomeata
Copy link
Contributor

nomeata commented 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:

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?

@nomeata 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
@niccolomarcon
Copy link

Having the same issue!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants