codesandbox / codesandbox/codesandbox-client
Folders are not visible at user profile
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
While visiting any user profile, e.g., mine is https://codesandbox.io/u/ditectrev, there are no CodeSandboxes despite the fact they're all public, in a folder. I was in touch with James A. from Support, he said it's intentional, but I'm curious if others are feeling the same as me it should be there, very basic feature. If I look at CodePen, its content inside folders, so-called "collections", are visible https://codepen.io/BlogFire/collections/ & https://codepen.io/Mohammed-Hamza_Pakistan/collections/ & ...
How has this issue affected you? What are you trying to accomplish?
It's not showing my CodeSandboxes.
To Reproduce
Go to any user profile that has public folders, for example, https://codesandbox.io/u/ditectrev
Link to sandbox: link
Your Environment
| Software | Name/Version |
|---|---|
| Сodesandbox | any |
| Browser | any |
| Operating System | any |
Screenshots
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 reproducing the behavior on a user profile with public folders, such as the linked profile, and inspect the profile UI and folder listing entry points. Done means public sandboxes contained in folders are visible from the owner's profile, with existing profile behavior preserved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100