[docs-infra] Lock versions on Codesandbox examples
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 99.1k
- Forks
- 32.5k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 106
Description
Summary 💡
In order to provide clarity and remove misunderstandings, it would be great if we can lock the versions in the Codesadnbox examples. The main reason is that sometimes it can happen that an issue is reported but by the time we check the reproduction case it has already been fixed.
If we have locked versions in the examples listed in the docs we can know exactly the versions the problem has occurred and compare it with the current latest.
Search keywords:
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
No files, tests, or entry points are named in the issue. Start by locating the Codesandbox examples listed in the documentation and identify where their dependency versions are defined. Done means the documented examples use locked versions so reproductions remain tied to known versions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- documentation, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100