Skip to content
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

Bump dependency versions #1949

Merged
merged 1 commit into from
Oct 11, 2021
Merged

Bump dependency versions #1949

merged 1 commit into from
Oct 11, 2021

Conversation

martijnbastiaan
Copy link
Member

Related: commercialhaskell/stackage#6217

  • Write a changelog entry (see changelog/README.md)
  • Check copyright notices are up to date in edited files

@phadej
Copy link

phadej commented Oct 10, 2021

I see the

    • Couldn't match expected type ‘GHC.Exts.Item
                                      aeson-2.0.1.0:Data.Aeson.Types.Internal.Object’
                  with actual type ‘(a0, Value)’

failure.

I will add the IsList (KeyMap v) instance in the next minor aeson release. It would be nice if you can report it though, so I don't forget.

parseWithRead field obj = do
v <- obj .:? field
case readMaybe =<< v of
Just a -> pure a
Nothing -> fail $ "Could not read field: " <> Text.unpack field
Nothing -> fail $ "Could not read field: " <> show field
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why this change? Do you want quotation marks around the field name?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It was a low-effort / good-enough fix for aeson moving to their Key datatype (as opposed to Text).

mergify bot pushed a commit that referenced this pull request Oct 11, 2021
Related: commercialhaskell/stackage#6217
(cherry picked from commit 7267499)

# Conflicts:
#	cabal.project
#	clash-ghc/clash-ghc.cabal
#	clash-lib/clash-lib.cabal
#	clash-prelude/clash-prelude.cabal
alex-mckenna pushed a commit that referenced this pull request Oct 11, 2021
alex-mckenna pushed a commit that referenced this pull request Oct 11, 2021
alex-mckenna pushed a commit that referenced this pull request Oct 11, 2021
alex-mckenna pushed a commit that referenced this pull request Oct 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants