New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Break into combinator/backend packages #25
Comments
Yes, this is definitely a good idea. I'm actually surprised I didn't have a ticket listing this. If you or anyone else wanted to get started working on this, I would definitely merge in a PR, or help clean it up. |
Thanks, I'll get started! |
@imalsogreg I also have an issue about breaking up stuff that is currently in the If doing that would help you with this issue, please feel free to do what is necessary 👍 |
This is the directory structure I have in mind - trying to stick to the style you are using already:
Open to suggestions! Are you bothered by having to maintain two hackage packages instead of one? |
We use
servant-checked-exceptions
in the frontend, and would like to avoid a transitive dependency onservant-server
,servant-client
,conduit
etc.What do you think of having two packages here
servant-checked-exceptions-core
(just types and pure functions) andservant-checked-exceptions
(instances and functions that depend on server-side code)?The text was updated successfully, but these errors were encountered: