nspcc-dev / nspcc-dev/neofs-dev-env
`wallet/wallet.json` is useless
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 10
- Forks
- 25
- PR merge metrics
- No merged PRs in 30d
Description
With https://github.com/nspcc-dev/neofs-dev-env/pull/238/commits/61fd192eaa410985e14d5466eb2a966c137cb545 that wallet becomes as useful as any other just-generated wallet. None of make commands deposits on it, no container can be created with it, etc. But on the other hand it is still mentioned in README (and in doc dir too).
I would add a separate make target that replenishes wallet/wallet.json and add it as a prerequisite for any up command. @roman-khimov
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading wallet/wallet.json, the referenced README section, and docs/chain.md, then inspect the Make targets behind the up commands. Check how the wallet is currently generated or replenished and verify the affected up commands use the refreshed wallet; done means the documented wallet is usable and the relevant environment commands work with it.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100