Open An Org button presented when no Salesforce Project is open
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- developer-experience, frontend
Research direction
Reproduce the issue by creating a Code Builder environment, closing the folder through File > Close Folder, and observing the “Let's Get You Started” screen. Inspect how the .vscode/settings.json mechanism hides this screen in Salesforce projects; done means the irrelevant screen and “Connect an Org” button no longer appear in this context.
Written by the indexing model from the issue text.
Description
Describe the bug
If I close a project in Code Builder, I am presented with a "Let's Get You Started" screen which has the option to Connect a Salesforce Org. But this will not work because the Salesforce tools don't open up unless I have a Salesforce project open, so this option should not actually be presented.
To Reproduce
Steps to reproduce the behavior:
- Create a new Code Builder environment
- Click "Hamburger" -> File -> Close Folder
- "Let's Get You Started" screen appears with blue button to open a Salesforce Org
Expected behavior
No "Connect an Org" button should appear, it's not relevant in this context
Screenshots
Desktop (please complete the following information):
- OS: any
- Browser: any
Smartphone or other device (please complete the following information):
N/A
Additional context
Actually, it would be nice for this screen to not show up at all in this context, because, since the mechanism to hide this screen is via the .vscode/settings.json file in a Salesforce project, and this isn't a Salesforce project, it means this screen shows up every single time you close a project directory. They may not be what a user wants after they've used a Code Builder environment for a while.
- Dominant language
- No language data
- Stars
- 35
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from forcedotcom/code-builder-feedback
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
forcedotcom/code-builder-feedback#273 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
forcedotcom/code-builder-feedback#265 · 2 comments ·
-
type:enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
forcedotcom/code-builder-feedback#262 · 1 comment ·
All issues in forcedotcom/code-builder-feedback
Similar issues
-
Adding SIMD typesOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
deltareview treats a line-range citation as an unknown path, firing the delta-review pass spuriouslyOpenagent-butler-finding bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
jordansmall/spindrift#4366 ·
Maintainers usually reply within 1 day
-
upstream update
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
conan-io/conan-center-index#31098 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
cvss-severity:high devguard l3montree-cybersecurity/.../devguard-documentation pkg:devguard/l3montree-c.../devguard-documentation risk:low state:open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
l3montree-dev/devguard-documentation#338 · 1 comment ·