codesandbox / codesandbox/codesandbox-client
wrong files are fetched for GitHub project
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
Extra files are shown in the explorer. See GitHub: https://github.com/algolia/create-instantsearch-app/tree/templates/autocomplete
vs codesandbox:
That folder actually exists, but is a sibling to the /autocomplete folder, not inside of it
How has this issue affected you? What are you trying to accomplish?
confusing files show up, and cause people to edit things that aren't displayed
To Reproduce
open the sandbox: https://codesandbox.io/s/github/algolia/create-instantsearch-app/tree/templates/autocomplete
see that the files aren't the same as on GitHub: https://github.com/algolia/create-instantsearch-app/tree/templates/autocomplete
Link to sandbox: link
Your Environment
| Software | Name/Version |
|---|---|
| Сodesandbox | 52d0d0108 |
| Browser | Safari |
| 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 with the CodeSandbox GitHub project import for the templates/autocomplete tree and compare its fetched files with the linked GitHub directory. Reproduce using the provided CodeSandbox link; done when the explorer matches the GitHub tree and does not show the sibling folder's files inside autocomplete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100