Sean Parsons

@kevinmeredith I was pointing out the manual solution, a generic solution would likely want to invoke the same kind of code. It would definitely be a nice thing to have...

Surely it would need an inverse for the decoder?

I'm not hugely bound to making a filter method that honours the needs of for comprehensions in Scala if requiring a message like the DecodeJson.validate better suits our needs.

I'm thinking we might bin this example as it doesn't really apply to the current code.

@tylerjharden Please feel free to look into implementing it, I can provide assistance if necessary.

Hmmm, that's interesting, I'm slightly worried it's satisfying a niche case but I'll keep this here for now and wont close it.

I don't doubt it's out there, it's more that each edge case feature we support is more potential weight to maintain.

Yes, but it's not really the forum for questions like this. It would be easier to diagnose if we had some example JSON that you were experiencing an error with.

Something like: ``` json"""{"key":$value}""" ``` ? I can see that being quite handy for sure, I'm just pondering how it would work, as we'd pretty much need a duplicate of...

@briantopping Do you mean this: http://argonaut.io/doc/codec/