Sean Chalmers

@whittle This is due to the use of diamond paths (``) within Obelisk combined with the environment variable `NIX_PATH` not being set. We've resolved it on the `develop` branch and...

Similar issue: #633

`Natural` isn't an impediment, I'm using the type system to prevent negative indentation values. The actual issue is that the docs have fallen out of step with the type signature,...

That's understandable, I think we're all a bit complacent when it comes to use of values that are "just a number", when in fact those numbers have a purpose and...

You can use either [`maybeOrNull`](https://hackage.haskell.org/package/waargonaut-0.5.2.2/docs/Waargonaut-Encode.html#v:maybeOrNull) or [`maybe`](https://hackage.haskell.org/package/waargonaut-0.5.2.2/docs/Waargonaut-Encode.html#v:maybe). These can be combined in a few different ways to handle optional fields, as well as optional values. Some [examples are here](https://github.com/qfpl/waargonaut/blob/master/test/Main.hs#L200), but...

You've plenty of options for how you choose to encode this, which is kind of the point of the library. :) Some alternatives: ```haskell encodePropertyA :: Applicative f => E.Encoder...

Waargonaut should be able to support that as well, although giving it a quick poke it is not as straight-forward as I remember. I might have to play with that...

Hacked out a thing... ```haskell -- Don't have to care what 'f' is here newtype ObjKV f a = ObjKV { envKV :: a -> JObject WS Json -> f...

I'm not sure that's really "issue" worthy, but I would happily accept a PR for such a thing. :+1: ```haskell import qualified Data.ByteString.Char8 as B8 encodeByteStringChar8 :: Applicative f =>...

Quite possible, as `ByteString.Char8` is limited to the latin1 charset which is a subset of what the JSON RFC allows. So you could see how well it goes to just...