mirror of
https://github.com/nspcc-dev/neo-go.git
synced 2026-03-01 04:28:51 +00:00
Extend wallet.Wallet API to allow saving wallet to a various byte streams #1200
Labels
No labels
I1
I2
I3
I4
S1
S2
S3
S4
U0
U1
U2
U3
U3
U4
blocked
bug
bug
cli
compiler
config
config
consensus
dependencies
discussion
documentation
enhancement
epic
feature
go
good first issue
help wanted
neotest
network
oracle
performance
question
rpc
security
smartcontract
task
task
task
test
vm
wallet
windows
windows
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
nspcc-dev/neo-go#1200
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @cthulhu-rider on GitHub (Oct 23, 2023).
according to docs, the wallet may be written to various byte streams. Instead, package doesn't provide any option to customize output stream other than filepath
suggest to either fix docs or support the documented functionality
@AnnaShaleva commented on GitHub (Oct 23, 2023):
The ability to write wallet to a custom stream may be useful, thus, I suggest to leave the doc as is and implement the custom output (although it may require some CLI/wallet refactoring).
@AnnaShaleva commented on GitHub (Dec 11, 2023):
@cthulhu-rider, is there any special demand to use anything except file to store the wallet? Or maybe @roman-khimov.
If not, then https://github.com/nspcc-dev/neo-go/pull/3255#discussion_r1422303697 solves this issue.
@cthulhu-rider commented on GitHub (Dec 11, 2023):
right now no
@roman-khimov commented on GitHub (Dec 11, 2023):
We have this API since like forever and it was always sufficient, so I'd adjust the documentation for now and that's it. API extensions can be left for the future.
@AnnaShaleva commented on GitHub (Dec 12, 2023):
Good, then let's exclude this issue from 0.105.0, the doc itself is fixed in #3255.