eeva/servant
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity
No description
1603 commits 52 branches 61 tags 9.2 MiB
Haskell 98.2%
Shell 1.4%
Nix 0.4%
Find a file
Oleg Grenrus 8574d8d2a9 Send Accept header in servant-client 
Fixes #858. The bug was introduced in servant-client-core refactor
(servant-client-0.12).

See 8973cf56f1/servant-client/src/Servant/Common/Req.hs (L151-L179)
for the unbroken variant in servant-client-0.11
2017-11-10 23:28:26 +02:00
doc Fix formatting in doc/examples.md 2017-11-06 13:08:29 +02:00
scripts switch ci to stack and add ci cron job to test hackage breakage 2016-08-17 14:12:12 +02:00
servant Fix typo in changelog 2017-11-08 12:50:06 +02:00
servant-client Send Accept header in servant-client 2017-11-10 23:28:26 +02:00
servant-client-core Bump versions and update changelogs. 2017-11-06 11:24:48 +02:00
servant-docs Bump versions and update changelogs. 2017-11-06 11:24:48 +02:00
servant-foreign Update changelogs 2017-11-06 12:35:43 +02:00
servant-server Add HoistSpec to other-modules of spec 2017-11-07 14:12:19 +02:00
.gitignore Add hoistServer to HasServer 2017-09-14 12:04:34 +03:00
.stylish-haskell.yaml Contributing 2015-08-17 23:50:42 +02:00
.travis.yml Bump versions and update changelogs. 2017-11-06 11:24:48 +02:00
cabal.project Bump versions and update changelogs. 2017-11-06 11:24:48 +02:00
CONTRIBUTING.md Mention servant-contrib repository 2017-01-20 20:20:10 +02:00
HLint.hs Contributing 2015-08-17 23:50:42 +02:00
README.md Add release process outline [ci skip] 2017-11-07 19:34:47 +02:00
servant.png Update READMEs 2015-04-20 15:48:37 +02:00
sources.txt Move servant-js to own repo 2016-10-08 15:08:07 +01:00
stack-ghc-7.8.4.yaml Continuing fix to build on 7.8.4 2017-10-06 13:03:27 +11:00
stack-ghc-7.10.3.yaml More reorganization 2017-09-14 09:54:13 -04:00
stack-ghc-8.2.1.yaml Review fixes 2017-09-14 13:21:53 -04:00
stack.yaml Use http-types-0.10 in stack.yaml 2017-10-23 08:57:56 +03:00

README.md

servant - A Type-Level Web DSL

servant

Getting Started

We have a tutorial that introduces the core features of servant. After this article, you should be able to write your first servant webservices, learning the rest from the haddocks' examples.

The central documentation can be found here. Other blog posts, videos and slides can be found on the website.

If you need help, drop by the IRC channel (#servant on freenode) or mailing list.

Version history

This table lists the versions of some servant- libraries at the point of release of servant package.

| | 0.10 | 0.11 | 0.12 | | ------------------- | -------- |---------------------| | servant | 0.10 | 0.11 | 0.12 | | servant-blaze | 0.7.1 | ? | ? | | servant-cassava | 0.7 | ? | ? | | servant-client | 0.10 | 0.11 | 0.12 | | servant-docs | 0.10 | 0.11 | 0.11.1 | | servant-foreign | 0.10 | 0.10.0.1 | 0.10.2 | | servant-js | 0.9.1 | ? | ? | | servant-lucid | 0.7.1 | ? | ? | | servant-mock | 0.8.1.1 | ? | ? | | servant-server | 0.10 | 0.11 | 0.12 | | servant-swagger | 1.1.2.1 | ? | ? |

Contributing

See CONTRIBUTING.md

Release process outline (by phadej)

  • Update changelog and bump versions in master
    • git log --oneline v0.12.. | grep 'Merge pull request' is a good starting point (use correct previous release tag)
  • Create a release branch, e.g. release-0.13, and protect it from accidental force pushes.
    • Release branch is useful for backporting fixes from master
  • Smoke test in servant-universe
    • git submodule foreach git checkout master and git submodule foreach git pull to get newest of everything.
    • cabal new-build --enable-tests all to verify that everything builds, and cabal new-test all to run tests
      • It's a good idea to separate these steps, as tests often pass, if they compile :)
    • See cabal.project to selectively allow-newer
    • If some packages are broken, on your discretisation there are two options:
      • Fix them and make PRs: it's good idea to test against older servant version too.
      • Temporarily comment out broken package
    • If you make a commit for servant-universe, you can use it as submodule in private projects to test even more
  • When ripples are cleared out:
    • git tag -s the release
    • git push --tags
    • cabal sdist and cabal upload