-
Notifications
You must be signed in to change notification settings - Fork 1
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
feat: resolver rebased #5
base: main
Are you sure you want to change the base?
Conversation
da87029
to
43250ef
Compare
1b4d2a5
to
658923f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd probably just drop the use of identity_iota::resolver::Resolver
in favor of a custom structure (HashMap
??) to get the right client for the right network.
If identity_iota_core::rebased::migration::identity::get_identity
is exposed by identity_iota
I'd probably use that to resolve since it returns a Result<Option<Identity>>
allowing you to easily handle 500 error as well as 404 (without having to look into the error message).
I have opted to use the |
0e61fd4
to
cffbf21
Compare
@itsyaasir good job! Do you mind waiting a bit before merging this? RN we are reworking a bit DID resolution on Rebased and I feel these changes should account for that as well. |
- Updated the `.env.sample` to include new network configurations for testnet, devnet, and custom networks. - Modified `Cargo.toml` to bump the `identity_iota` and `identity_storage` dependencies to version `v1.6.0-alpha.1`. - Adjusted the `Dockerfile` to set the `NETWORK` environment variable to `devnet`. - Enhanced the `README.md` to clarify network configuration options and provide examples for single and multiple network setups. - Refactored `lib.rs` to implement a new `Network` enum for better handling of network configurations and client initialization. - Updated tests to reflect changes in network handling and ensure compatibility with the new configurations.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Make sure the tests run succesfully
tests/common/mod.rs
Outdated
// WORKAROUND: Ignore the resullts of the faucet request as sometime the | ||
// request will fail but the funds will be | ||
// available. | ||
let _ = request_faucet_funds(address).await; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mmmm not sure if this is desirable... Can't we test on a localnet instead?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can but we will have to publish the package which is not available here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Anyone even what I did didn't work.
Description of change
This pull request includes several significant changes aimed at updating the resolver to the latest rebased IOTA.
Changes include:
Links to any relevant issues
Type of change
How the change has been tested
Change checklist