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
Librarification #95
Comments
Coming from #289, to be honest I didn't realize you were already using |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It would be nice to expose a library interface, to enable projects to build on top of
xh
along the lines of http-prompt. It would also help with #88.This could be a pretty big change. We'd have to decide what to expose and commit to not breaking compatibility. Refactoring would become harder the more we expose.
Some concrete steps would be:
main
pub
topub(crate)
#[non_exhaustive]
to certain public enumsanyhow
It could help to have a consuming project that lives in the same repository (in a workspace).
At first glance, we might not have to expose that much, see how http-prompt calls it. But I haven't looked at other projects, and a richer API might be a lot more convenient.
Breaking the public interface after 1.0 would mean incrementing the major version number. I can think of a few approaches:
xh_core
) that can increment its major version freely, while thexh
package becomes a wrapper around it with more conservative versioning.The text was updated successfully, but these errors were encountered: