Skip to content
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

Converting to monorepo #100

Open
ten3roberts opened this issue Aug 15, 2023 · 1 comment
Open

Converting to monorepo #100

ten3roberts opened this issue Aug 15, 2023 · 1 comment
Assignees
Labels
C-enhancement Category: New feature or request P-important (Priority) something that contributes towards achieving the long term goals of the project

Comments

@ten3roberts
Copy link
Contributor

It would be useful to convert the eyre, color-eyre, stable-eyre et.al. It would improve the discoverability of the different subcrates, as well as provide a single place where issues can be reported.

The current separate repositories makes it difficult for users to know where to report the errors as it may not initially be obvious if the source is in Eyre or an eyre hook implementer. It is a case of the classic "where should it go"

Merging them will improve the ease of issue creation and discovery, as well as overview.

The proposed structure will also improve ease of integration testing and examples and side-by-side development between the crates.

@ten3roberts ten3roberts added the C-enhancement Category: New feature or request label Aug 15, 2023
@ten3roberts
Copy link
Contributor Author

Furthermore, it would provide a common CI between the crates, which ensures that each of the subcrates, such as color-eyre also gets tested and a single PR can test regressions on both the core eyre as well as our crates that use eyre at the same time.

@yaahc yaahc added the P-important (Priority) something that contributes towards achieving the long term goals of the project label Aug 16, 2023
@ten3roberts ten3roberts self-assigned this Mar 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-enhancement Category: New feature or request P-important (Priority) something that contributes towards achieving the long term goals of the project
Projects
None yet
Development

No branches or pull requests

2 participants