codesandbox / codesandbox/codesandbox-client

Navigating to codesandbox switches org/user

Open
#5,035 11 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

💬 Discussion 🤔 Improvement UX
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

I have my personal account and an org account. The org accounts owns a template. When I navigate to the template codesandboxes switches the current "user" in the top left to the org account. When I fork that template the fork is owned by the org account when it should be owned by me.

How has this issue affected you? What are you trying to accomplish?

It's mildly annoying since I "just have to move" the newly created sandboxes to my account but that's easy to forget when quickly prototyping

To Reproduce
  1. Setup org
  2. Create template from org
  3. Switch to personal account
  4. Navigate to template

Recording of above reproduction steps

Your Environment
Software Name/Version
Сodesandbox 2e8e79915
Browser Chrome 86
Operating System Ubuntu 18.04

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue using the listed steps: create an organization template, switch to a personal account, and navigate to that template in Chrome. Done means navigation keeps the personal account selected and a fork is owned by the personal account rather than the organization.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.