The json-litobj package

This is a package candidate release! Here you can preview how this package release will appear once published to the main package index (which can be accomplished via the 'maintain' link below). Please note that once a package has been published to the main package index it cannot be undone! Please consult the package uploading documentation for more information.

[maintain]

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


[Skip to ReadMe]

Properties

Versions0.1.0.0, 0.1.0.0
Change logNone available
Dependenciesbase (==4.7.*), json (==0.9.*) [details]
LicenseBSD3
AuthorJonathan Kochems
Maintainerjonathan.kochems@gmail.com
CategoryText
Home pagehttps://github.com/jonathankochems/json-litobj
Source repositoryhead: 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)
UploadedSun Aug 23 20:10:23 UTC 2015 by jonkoc

Modules

[Index]

Downloads

Maintainers' corner

For package maintainers and hackage trustees


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:

{ "foo" : "bar" }

{ 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