forcedotcom / forcedotcom/code-builder-feedback
Open An Org button presented when no Salesforce Project is open
- Lenguaje dominante
- Sin datos de lenguaje
- Estrellas
- 35
- Forks
- 2
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Descripción
**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:
1. Create a new Code Builder environment
2. Click "Hamburger" -> File -> Close Folder
3. "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.
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Línea de trabajo
Reproduce el problema creando un entorno de Code Builder, cerrando la carpeta mediante File > Close Folder y observando la pantalla “Let's Get You Started”. Inspecciona cómo el mecanismo .vscode/settings.json oculta esta pantalla en los proyectos de Salesforce; se considera terminado cuando la pantalla irrelevante y el botón “Connect an Org” ya no aparezcan en este contexto.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Área
- developer-experience, frontend
- Tipo de issue
- Error
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Estancado
- Claridad
- Bastante claro
- Aptitud para principiantes
- 35/100