-
-
Notifications
You must be signed in to change notification settings - Fork 11
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
Refactor Runtime #44
Refactor Runtime #44
Conversation
@dr-orlovsky I agree that the term |
Yes, that was a thought to get things in line with RGB naming. Both are StoredWallets - they are differentiated by their crate prefix. Users of one will not use the other - and wise verse |
I don't think this is the case. Check the integration tests PR where we use both the |
I ended up with some larger refactoring due to discovery of a bug when the wallet data are not always saved to the disk. Thus, I have refactored all FS-related workflows to ensure that the data are always saved. As a side-effect, I got rid of few types and traits which become redundant, thus the APIs and namings have become clearer and simpler. This PR has two counterparts: |
it seems there's an error with features usage:
by adding the |
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.
tACK 30ae979
Runtime
is misleading since there might be many different runtimes for different purposes. This one is quite simple one - it just reads and writes wallet to a file.To use it one will also need an update in RGB wallet: RGB-WG/rgb#216@zoedberg there is nothing to review actually, I set you as a reviewer to inform about the name change if you are using this type (I assume you are not).UPD: I found a bug in the implementation of
StoredWallet
which doesn't automatically save the data upon modification. As a part of the solution, I have refactoredStoredWallet
intoWallet
itself.UPD2: I ended up with some larger refactoring due to the discovery of a bug when the wallet data are not always saved to the disk. Thus, I have refactored all FS-related workflows to ensure the data are always saved. As a side-effect, I got rid of a few types and traits which became redundant, thus the APIs and namings have become clearer and simpler.
This PR has two counterparts: