Skip to content

aeson 2.0 compatibility #887

@maralorn

Description

@maralorn

As of a few days ago, there is a new bower-json version which supports aeson 2.0.

Now to support aeson 2.0 there are only the build errors in spago itself left. I get the following build error, when trying to build with aeson 2.0, but it might be masking more:

src/Spago/Bower.hs:112:33: error:
    • Couldn't match type: Data.Aeson.KeyMap.KeyMap Value
                     with: HashMap k0 a0
      Expected: HashMap k0 a0
        Actual: Object
    • In the second argument of ‘HashMap.member’, namely ‘info’
      In the expression: HashMap.member "version" info
      In a stmt of a 'do' block:
        if HashMap.member "version" info then
            pure $ Bower.VersionRange $ "^" <> version
        else
            pure $ Bower.VersionRange $ repo <> "#" <> version
    |
112 |     if HashMap.member "version" info
    |                                 ^^^^

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions