Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Only shows components in the force-app directory #84

Open
BrettMN opened this issue Oct 12, 2020 · 2 comments
Open

Only shows components in the force-app directory #84

BrettMN opened this issue Oct 12, 2020 · 2 comments

Comments

@BrettMN
Copy link

BrettMN commented Oct 12, 2020

Describe the bug
A clear and concise description of what the bug is.

If the sfdx-project.json specifies a different path as default the local server shows that path (package) as being available but it does not find any components from that path.

If the directory is changed to force-app, even without updating the sfdx-package.json, the components appear.

To Reproduce
Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

use a path besides force-app for you package

Expected behavior
A clear and concise description of what you expected to happen.

list the components in the directory specified as default.

Screenshots
If applicable, add screenshots to help explain your problem.

{
    "packageDirectories": [
        {
            "path": "questions",
            "default": true
        }
    ],
    "namespace": "",
    "sfdcLoginUrl": "https://login.salesforce.com",
    "sourceApiVersion": "50.0"
}

Screen Shot 2020-10-11 at 8 24 23 PM

Desktop (please complete the following information):

  • OS: [e.g. iOS]
  • Browser [e.g. chrome, safari]
  • Version [e.g. 22]

MacOS 10.15.7
Chrome 85.0.4183.121

Smartphone (please complete the following information):

  • Device: [e.g. iPhone6]
  • OS: [e.g. iOS8.1]
  • Browser [e.g. stock browser, safari]
  • Version [e.g. 22]

Additional context
Add any other context about the problem here.

@stale
Copy link

stale bot commented Oct 19, 2020

This issue has been automatically marked as type:bug-p3 because it has not had recent activity.

@stale stale bot added the type:bug-p3 label Oct 19, 2020
@git2gus
Copy link

git2gus bot commented Oct 19, 2020

This issue has been linked to a new work item: W-8231933

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant