@hackage geojson1.3.0
A thin GeoJSON Layer above the aeson library
Categories
License
BSD-3-Clause
Maintainer
Dom De Re
Links
Versions
Deprecated
Dependencies (8)
- aeson >=0.9 && <0.10
- base <5 && >=4
- lens >=4.11 && <4.12
- semigroups >=0.16 && <0.17
- text >=1.2 && <1.3
- transformers >=0.3 && <0.5 Show all…
Dependents (5)
@hackage/poseidon-postgis, @hackage/wkt-geom, @hackage/acme-everything, @hackage/esqueleto-postgis, @hackage/reanimate
Package Flags
small_base
(on by default)
Choose the new, split-up base package.
geojson

A thin GeoJSON Layer above the aeson library
Building the project
Install the dependencies with:
cabal install --only-dependencies
Optionally add --enable-tests if you intend to run the unit tests
The project must be "configured" at least once everytime geojson.cabal changes, this can be done with:
cabal configure
If you wish to run the unit tests you will have to run:
cabal configure --enable-tests
Then finally build it with:
cabal build
See cabal build --help for more build options.
Running Unit Tests
After running cabal build, you can run the unit tests with the command:
cabal test
Adding Unit tests
Unit tests are written with [doctest] doctest-github, for instructions on how to add unit tests see the doctest [User Guide] doctest-userguide.
Currently only files in the src/ directory are searched for tests, it is assumed that the code in main/
is a thin layer of code that uses modules from src/.
Development: Cabal Dependency Hell?
Cabal's great, but when you are developing a few different projects with their own dependency chains, sometimes installing all your libraries to the same place causes problems,
Consider trying [cabal-dev] cabal-dev. In terms of using it, all thats required is replacing cabal with cabal-dev in all the above command lines.
It will download and install all the dependencies for your project and install them in a cabal-dev/ directory in your project directory, and they will only be used for this project.
Those with newer versions of cabal (>= 1.18 I think) can skip cabal-dev and instead run cabal sandbox init, and just start runnign the above instructions
as is from cabal install --only-dependencies