🎉 sangria-akka-http -> sangria-http & subprojects

[nickhudkins]

This is an attempt to move this repo towards sangria-http with sub projects providing specific implementations of each piece. It is currently just opened for discussion.

The following convention is used: sangria-http-${HttpFramework}-${SerializationLibrary}

sangria-http
sangria-http-akka
sangria-http-akka-circe

[blast-hardcheese]

Good stuff! Would this end up prompting renaming the project from sangria-akka-http to sangria-http?

One of the things I've been trying to work around is how to remain agnostic around which http library and json library are used, since akka-http+circe is distinct from http4s+circe, but a lot of the core stuff (instances and whatnot) is similar. Maybe sangria-akka-http, sangria-circe, and sangria-akka-http-circe to tie them together?

I don't know if the problems Sangria has have enough overlap in this way to be a useful observation

[nickhudkins]

Hey @blast-hardcheese that's some of the hope. You can see sangria-marshalling-api is the inspiration here. sangria-circe simply fills in an implementation of the sangria-marshalling-api. My hope here is that sangria-http would potentially serve a very similar thing. sangria-http-akka would fill in the akka specific impl, and then sangria-http-akka-circe would take sangria-circe and circe and akka-http to all be tied together

[performantdata]

% Test ?

[performantdata]

Doesn't playground.html belong in core?

[performantdata]

At this point, might be less hassle if we push #14 before this.

[yanns]

@nickhudkins I really like this change, and would like to add more support, like for http4s.
Would you have the energy to fix all conflicts and push this forward?