Closed Kayanski closed 7 months ago
Latest commit: |
1d8c7e2
|
Status: | ✅ Deploy successful! |
Preview URL: | https://e0853a05.cw-orchestrator.pages.dev |
Branch Preview URL: | https://fix-mock-bech32.cw-orchestrator.pages.dev |
Attention: 127 lines
in your changes are missing coverage. Please review.
Comparison is base (
3a79f71
) 65.4% compared to head (1d8c7e2
) 65.4%.
Did a bit of a refactor of the queries to make them API generic by relying on the difference in addr generation between the mock and bech32 impls.
I'm a bit confused by the bech32
module in core.rs
. Can we split these two type impls?
Did a bit of a refactor of the queries to make them API generic by relying on the difference in addr generation between the mock and bech32 impls.
I'm a bit confused by the
bech32
module incore.rs
. Can we split these two type impls?
Haha gotta love the refactor hack :)
--> Yes we can split the 2 impls in separate files, sure ! The differences are very subtle :)
Another question we should ask ourselves is if we want to keep supporting impl Into<String>
in our address fields?
Another question we should ask ourselves is if we want to keep supporting
impl Into<String>
in our address fields?
See answer above? I think that it's really good to simplify the users life in case no bech32 verification is needed
This PR aims at introducing MockBech32 that enforces valid addresses Tests needs a little revamp (doc tests mostly), but that's a good looking implementation and usable by users.