codesandbox / codesandbox/codesandbox-client
GitHub repository sandboxes are not fetched
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 13.6k
- Forks
- 2.4k
- Avg merge
- 6d 19h
- Merged PRs (30d)
- 2
Description
🐛 bug report
Preflight Checklist
- I have read the Contributing Guidelines for this project.
- I agree to follow the Code of Conduct that this project
adheres to. - I have searched the issue tracker for an issue that matches the one I want
to file, without success.
Description of the problem
Hey @sannek / @lbogdan, it seems that certain repositories no longer correctly seem fetched. No information or files can be found:
I think this may be the same issue as happened back in September in https://github.com/codesandbox/codesandbox-client/issues/6109
How has this issue affected you? What are you trying to accomplish?
Examples in our documentation no longer work
To Reproduce
- https://codesandbox.io/s/github/algolia/doc-code-samples/tree/master/React%20InstantSearch/injected-content
- https://codesandbox.io/s/github/algolia/doc-code-samples/tree/master/React+InstantSearch/injected-content
Link to sandbox: https://codesandbox.io/s/github/algolia/doc-code-samples/tree/master/React%20InstantSearch/injected-content
Your Environment
| Software | Name/Version |
|---|---|
| Сodesandbox | 54f46eeec |
| Browser | Safari / Chrome |
| Operating System | macOS |
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 opening the linked CodeSandbox example and reproducing the missing files and information with the two GitHub tree URL variants provided. Check the related issue #6109 for prior context and use the reported Safari and Chrome environments. Done means the documented GitHub repository sandbox loads its files and information correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100