MetaMask / MetaMask/metamask-docs
Include min supported version for all Snaps features
Open
Nobody has claimed this yet.
snaps
snaps-unrefined-backlog
- Dominant language
- MDX
- Stars
- 861
- Forks
- 2.1k
- Avg merge
- 6d 10h
- Merged PRs (30d)
- 10
Description
Aside from stating whether a feature is specific to Flask or stable, we should also state the minimum supported version for all features, UI components, permissions, endowments, and entry points.
To-do: come up with a consistent way to do this.
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 reviewing the existing documentation for Snaps features, UI components, permissions, endowments, and entry points, noting how Flask or stable status is currently presented. Define a consistent minimum-version convention across those areas, then confirm that every listed documentation category applies it uniformly.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100