Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
CF: yesodweb/yesod#1602
CC: @snoyberg
This template takes
yesod-simple
and replacesclassy-prelude-*
with
rio
. I have checked that everything builds and runs out of thebox, and that the tests are green.
I have not (yet) used it in anger to develop an app, and I am but a
Yesod and RIO neophyte, so it needs careful reviewing.
Some points:
aeson
andyaml
were relaxed to allow those in thelatest lts release (13.25);
http-types
,yesod-newsfeed
andpersistent
was added withno bounds restrictions — what restrictions should we use
on these packages?
rio >= 0.1.8.0
: is my starting point — can we relax theupper bound? What upper bound should we use?
rio
to work with the current stack I am hiding parts of therio
logging system (I guess these will be addressed bythis work).