json-litobj: Extends Text.JSON to handle literal JS objects.

[ bsd3, library, text ] [ Propose Tags ] [ Report a vulnerability ]

This module extends Text.JSON to enable the decoding of strings containing literal JS objects.


[Skip to Readme]

Modules

[Index]

Downloads

Maintainer's Corner

Package maintainers

For package maintainers and hackage trustees

Candidates

Versions [RSS] 0.1.0.0
Dependencies base (>=4.7 && <4.8), json (>=0.9 && <0.10) [details]
License BSD-3-Clause
Author Jonathan Kochems
Maintainer jonathan.kochems@gmail.com
Category Text
Home page https://github.com/jonathankochems/json-litobj
Source repo head: git clone git://github.com/jonathankochems/json-litobj.git -b develop
this: git clone git://github.com/jonathankochems/json-litobj.git -b master(tag hackage-0.1.0.0)
Uploaded by jonkoc at 2015-08-23T20:13:32Z
Distributions
Reverse Dependencies 1 direct, 0 indirect [details]
Downloads 924 total (4 in the last 30 days)
Rating (no votes yet) [estimated by Bayesian average]
Your Rating
  • λ
  • λ
  • λ
Status Docs uploaded by user
Build status unknown [no reports yet]

Readme for json-litobj-0.1.0.0

[back to package description]

json-litobj Build Status codecov.io BSD3 License

This module extends Text.JSON to enable the decoding of strings containing literal JS objects. In particular, it relaxes the restriction that fields in JSON objects must be strings.

For example:

  • JSON conformant:

{ "foo" : "bar" }

  • literal JS object:

{ foo : "bar" }

Documentation

The haddock documentation can be found on hackage.

Motivation

I wanted to parse JSON responses from various websites with Text.JSON. Unfortunately, I ran into parsing errors due to literal JS objects included in the answer strings. Since literal JS object are not really part of the JSON format I started this module to work around this problem.

Contributing

If you feel that this module is missing something useful which should be part of a more ``permissive'' JSON parsing please consider a contribution.

To contribute:

  1. fork this repository
  2. create a feature branch
  3. commit and push your code to your feature branch
  4. create a pull request to this repository