Use aeson's token stream for json parser

I haven't thought deeply about your use case, but I almost always default to aeson

[awalterschulze]

I have also heard good things about aeson and it was the first package I checked out, but since I don't know the field names I want to parse the usage examples was not really a good fit.
If you have a more general example that you can point me to, that would be very much appreciated.

It will probably still work. I don't think I have used it for parsing fields to be determined at runtime yet... Aeson is used very widely (http://packdeps.haskellers.com/reverse/aeson) so browsing github on any of those repos should yield some useful examples.

As for tutorial style learning, I liked this https://artyom.me/aeson, although it has mixed reviews. There are a few fundamental concepts. Once you get those, you can use the API fluently. Some of those concepts depend on general Haskell patterns which you may or may not already know. If you hit a point where a general haskell pattern feels too foreign, then I would consider using the Haskell First Principles book to understand the concept you need to learn first.

[awalterschulze]

Thank you. I'll definitely have a look :)

[awalterschulze]

I have integrated aeson on a branch, but I have a problem.
https://github.com/katydid/katydid-haskell/tree/aeson

The Object that aeson decodes to is an unordered hashmap.

My validation language supports both ordered and unordered expressions, which means that the parser needs to preserve order.
Can you think of anyway that we can make aeson rather decode into some sort of ordered Hashmap?

This issue only seems to discuss order serializing, but not deserializing.
haskell/aeson#368

On this issue and the other question, I can't spend more time on this currently. Try posting narrow questions to Haskell Reddit. People usually respond.

[awalterschulze]

No problem. Thanks for all your time. I really appreciate it.

[awalterschulze]

I commented on the issue on aeson and will wait for a reply on that.

[awalterschulze]

waiting for haskell/aeson#560

[awalterschulze]

I think we should keep this open.
I know it has been a few years, but I still think this is worth doing.

[awalterschulze]

Aeson now supports token streams

haskell/aeson#996