realocate constants to their specific crates#1728
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1728 +/- ##
==========================================
- Coverage 23.45% 23.40% -0.05%
==========================================
Files 146 146
Lines 10918 10940 +22
==========================================
Hits 2561 2561
- Misses 8357 8379 +22
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
2b557e5 to
27eb03a
Compare
AFAIK, we moved all the constants to sv2-common because we were considering consolidating the imports directly from roles-logic, which in turn depends on stratum-common. However, I don't have much context on this, @GitGab19 might have more insight. |
yes, I'm aware of that this PR is still aligned with this strategy after all, stratum/protocols/v2/roles-logic-sv2/Cargo.toml Lines 15 to 22 in 2f7d66e the only exceptions would be and as described in #1458, ideally the strategy of standardizing dependency exporting actually revolves around both |
|
LGTM, I just left a couple of comments to be reviewed before merging this. |
ee1ffe7 to
b60f872
Compare
b60f872 to
6bedcd0
Compare
done by mistake on stratum-mining#1728
done by mistake on stratum-mining#1728
IMO the approach of #1642 was suboptimal
moving the contents from
const_sv2intostratum_commonwas a bit redundant, since we ended up still having all constants concentrated in one single placeconstants should live in the specific crates where they have contextual meaning