Simon Hengel

Results 312 comments of Simon Hengel

@moodmosaic done! Anything else you need? Changes: https://github.com/hedgehogqa/haskell-hedgehog/compare/93d1f1e508970c27d2c872facdc26610d202743a..d92399b8bc4376a867c7400989322f94cef7487b https://github.com/hedgehogqa/haskell-hedgehog/compare/ea5a0fe7dd527c85b3e701ed4e9d10955452d0ce..93d1f1e508970c27d2c872facdc26610d202743a

I'm gone use the git version for the time being. But once we have a release, all users will benefit from it, which I think will be a big improvement.

Make sure to add ```yaml tests: tinytools-test: build-tools: hspec-discover ``` to your `package.yaml`. (or `build-tool-depends: hspec-discover:hspec-discover` if you are using plain `.cabal`) This is needed if you want to build...

Also note that `cabal test all` may skip tests. You have to use `cabal test all --enable-tests` (sounds comical, but sadly it's true https://github.com/haskell/cabal/issues/5079). Alternatively, run `cabal configure --enable-tests --enable-benchmarks`...

Sounds good. 👍 In an ideal world we would derive the schema and documentation from the same representation that we use for parsing. However, I'm not sure how practical this...

We currently have our own ad-hoc generic machinery in [`Data.Aeson.Config.FromValue`](https://github.com/sol/hpack/blob/main/src/Data/Aeson/Config/FromValue.hs) that: - Allows us to warn on unknown fields - Allows for field aliases (and by extension for renaming of...

@NorfairKing looking at the example from the README, links to the generated output (schema, sample JSON, etc) could be a nice addition. I am not on a computer right now,...

> > @NorfairKing looking at the example from the README, links to the generated output (schema, sample JSON, etc) could be a nice addition. I am not on a computer...

For completeness, I think conceptually this is what we would want: ```haskell {-# LANGUAGE TypeFamilies #-} {-# LANGUAGE DataKinds #-} module Person where import Data.Coerce import GHC.Generics import GHC.TypeLits newtype...

> So maybe setting private: true could set license: NONE That is a good point; omiting `license` all together should have the same effect I guess. This also means that...