feat: make nodes configurable for IOTA resolvers #41
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oran-Dan
changed the title
7 tasks
daniel-mader
force-pushed
the
feat/resolver_new_with_node_url
branch
from
122f251 to
c65ccc6
Compare
daniel-mader
changed the title
daniel-mader
approved these changes
Jan 8, 2026
|
🎉 This PR is included in version 1.0.0-beta.7 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of change
The resolver needs to be easily configurable with any IOTA node url. Custom node urls often require basic authentication as well, so this has been made configurable too.
Links to any relevant issues
How the change has been tested
I've added new unit tests.
Old tests still pass.
Definition of Done checklist
Add an
xto the boxes that are relevant to your changes.