Closed Krasjet closed 4 years ago
The alternative implementation can be found here: https://github.com/Krasjet/servant-rawm/tree/merge. In this implementation, servant-rawm
defines the API and other packages defines the implementation.
It will cause some breaking changes, but it only requires three extra packages and can be easier to maintain. I personally prefer this solution.
@Krasjet If you recommend the other approach, then please open a PR for that as well.
Also, are you using servant-rawm professionally or anything? Would you be interested in helping maintain it moving forward?
Of course. It's used by one of my side projects (karasu). It's not professional or something, but I'm actively using it.
superseded by #16
This pull request separates client, docs, server, api, into four different packages to address the issue mentioned in #14.
The base package
servant-rawm
re-exports everything from sub-packages, so after the update, applications should compile without any modifications. If breaking changes are not a concern, we could mergeservant-rawm-api
andservant-rawm
to a single package.