-
Notifications
You must be signed in to change notification settings - Fork 0
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
Use aeson's token stream for json parser #6
Comments
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. |
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. |
Thank you. I'll definitely have a look :) |
I have integrated aeson on a branch, but I have a problem. 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. This issue only seems to discuss order serializing, but not deserializing. |
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. |
No problem. Thanks for all your time. I really appreciate it. |
I commented on the issue on aeson and will wait for a reply on that. |
waiting for haskell/aeson#560 |
I think we should keep this open. |
I haven't thought deeply about your use case, but I almost always default to aeson
The text was updated successfully, but these errors were encountered: