Summary

For some odd reason, if you have the word type as an attribute, it breaks syntax highlighting for everything that comes after. Only seems to be an issue with the script tag

Steps To Reproduce:

1. Open up a VF page
2. Page in

<apex:page>
    <script type=""  />
    <p>not formatted :/</p>
</apex:page>

Expected result

Syntax highlighting would be preserved

Actual result

It's not

Additional information

Summary

Would it be possible to format the file based of off the AST when saving a file? If it compiles, we can grab the AST and then format the document. This idea comes from Prettier and the JS community. Would anyone be interested or feasible with apex and the langauge server API?

Summary

There seems no feature to auto format Apex code nor linting warnings.
I have looked at this thread: https://github.com/forcedotcom/salesforcedx-vscode/issues/95 but not sure if it talks exactly the same problem

Steps To Reproduce:

1. Right click on the file content window, there is no format document option.
2. In javascript file, this option is available.

Additional information

Should I manually remove all unnecessary space and make the code aligned?

VS Code Errors Activating salesforce.salesforcedx-vscode-core Extension

After installing VS Code Ext pack, the core extension will not activate. CLI commands are not available from the command palette.

Steps To Reproduce:

1. Install VS Code.
2. Install VS Code Extension pack from within VS Code.
3. Clone sfdx-dreamhouse to local (or any valid sfdx project; doesn't seem to matter which)
4. Open sfdx project in VS Code as root folder
5. Attempt to run sfdx commands from command palette

Expected result

Should be able to run CLI commands from VS Code.

Actual result

Can't run sfdx CLI commands.

Additional information

VS Code Version: 1.15.1 (shell 1.6.6) win64

SFDX CLI Version: sfdx-cli/5.7.6-d42cf65 (windows-amd64) go1.7.5 sfdxstable

OS and version: Windows 7 Enterprise 6.1.7601 Service Pack 1 Build 7601

Summary

https://developer.salesforce.com/docs/atlas.en-us.eclipse.meta/eclipse/debugger_set_up_parent.htm

You have to contact support to get Apex Debug option enabled for your org.

Steps To Reproduce:

Go to System Permissions and there is no Apex Debug option.

Expected result

When you Enable DevHub or on any Scratch org to have Apex Debug option available without having to contact support.

Actual result

Not showing and have to contact support

Additional information

Feel free to attach a screenshot.

VS Code Version:

SFDX CLI Version:

OS and version:

Sorry if there's more appropriate place to ask this but is there a version of this for standard "Visual Studio" users and not just "Visual Studio Code" users? If not, is there a way to force the "Visual Studio Code" version of this into "Visual Studio"?

Summary

Trying to create a project using SFDX VS Code palette commands.
This has worked before, not sure what has changed (almost certainly on my end). However, the error message is incorrect and so I'm not sure how to fix.

Steps To Reproduce:

1. In VS Code, Ctrl+Shift+P then SFDX create project command.
2. Input name of project
3. Select root folder of project on a mapped network drive (eg., net use...) and path with space
4. Error message displays per screenshot below. Project seems to be created, but further SFDX commands fail.

Expected result

Error message reflects the problem the plugin is having.

Actual result

Error message suggests that folder does not exist, when it does.

Additional information

• Drive H: is a mapped network drive. Notice that it's missing in the error message

VS Code Version:
1.21.0

SFDX CLI Version:
Can't see this on the extension summary in VSCode, or in the changelog, or in the dependencies...possible to add a version number to the description? Unless I'm being an idiot.

OS and version:
Windows 10

Internal Work Item:
W-5171363

Summary

I have Salesforce Extensions for VS Code installed in my VS Code. Apparently whenever I start editing code (putting actual code into the class) the CPU usage for Code Helper and JAVA straight away increase to 100%, and everything in salesforcedx-vscode-apex such as code complete, check syntax, view outline stop working.

I tried disable the extension and the CPU usage became normal.

Could someone plz have a look what happened or maybe there is already a solution?

Steps To Reproduce:

1. Open VSCode
2. Start editing code

Expected result

CPU usage should be normal and vscode-apex functions should be able to run

Actual result

CPU usage increased and 10 secs later all vscode-apex related function stop working

Additional information

VS Code Version:
v1.18.1
SFDX CLI Version:
sfdx-cli/6.0.16-3780698 (darwin-x64) node-v8.6.0
OS and version:
macOS Sierra 10.12.6

Summary

Syntax highlighting in Apex does not seem to distinguish properly braces, accolades and other delimiters (block for instance). This makes the source code very monochromatic and hard to read.

Steps To Reproduce:

1. Open an Apex class

Expected result

The syntax highlighter should be able to recognize and properly categorize delimiters, like so many other languages do, with categories like meta.block, meta.brace, meta.tag, punctuation (or even better punctuation.section.array.begin)...

Actual result

Almost every character in a method is categorized as source.apex ou meta.method.apex, making the source code monochromatic and hard to read.

Additional information

Alomost every character has the same color in the screenshot below (even the regular expression is not recognized):

VS Code Version:
1.21.0

Functionality

To simplify executing anonymous apex (not using sfdx from the built-in VScode terminal window) a custom command should be implemented.

Implementation

• A new menu binding "SFDX: Execute Anonymous Apex" will be implemented. Also a menu addition (in "editor/context" for .cls and .trigger files).
• Input will be saved in temp file with random file name.
• Anonymous Apex command gets executed and temp file deleted. Output gets send to standard "Output" console window.

Missing 'engines' key in package.json of salesforce-utils-vscode

The develop branch cannot be used for launching the extensions. An error is raised that points to a missing engines key in the package.json of salesforce-utils-vscode.

Adding the key raises another error:
/.../salesforcedx-vscode/packages/salesforcedx-utils-vscode]: properties activationEvents and main must both be specified or must both be omitted

Removing the main key from the package.json solved that issue.

Steps To Reproduce:

• Clone the repo, make sure that you're in the develop branch.
• In VS Code, open the debug view and from the launch configuration dropdown, pick "Launch Extensions".
• The new VS Code windows opens with an error message.
• Add engines key to package.json:
• Re-launch from debug view - new error message appears.

Expected result

Launching the extensions without an error message.

Summary

When executing Apex tests from the VS Code editor, the code in the default scratch org is not refreshed prior to executing the tests. This causes unexpected results because the executing test may be different from the source code.

Steps To Reproduce:

1. Open a project with tests.
2. Find a test and introduce a semantic error in it.
3. Run the test by clicking the "Run test" link in the editor.

Expected result

Test should fail because of the semantic error.

Actual result

Test passes because an old version of the code is actually executing.

Additional information

VS Code Version:
1.21.0

SFDX CLI Version:
sfdx-cli/6.7.0-0b3aca2f1f (darwin-x64) node-v8.9.4

OS and version:
Mac 10.13.3

Summary

Can't run SFDX commands in VSCode terminal on Mac OS

Expected result

Creates Apex Class

Actual result

sfdx force:apex:class:create --classname testCLITool --template DefaultApexClass --outputdir src/classes ended with exit code 1

Starting SFDX: Create Apex Class

sfdx force:apex:class:create --classname testCLITool --template DefaultApexClass --outputdir src/classes
 ▸    autoupdate:: 'EACCES': EACCES: permission denied, mkdir
 ▸    '/Users/michaelgarfinkel/Library/Caches/sfdx/update.lock.readers.lock'
 ▸    'EACCES': EACCES: permission denied, mkdir
 ▸    '/Users/michaelgarfinkel/Library/Caches/sfdx/update.lock.readers.lock'
sfdx force:apex:class:create --classname testCLITool --template DefaultApexClass --outputdir src/classes ended with exit code 1

Additional information

VS Code Version: 1.21.0

SFDX CLI Version: 6.5.0

OS and version: MacOS High Sierra

Summary

after hit the Break point if i press F10, request had stopped message appear instead of Debugger move to next line of code at both places proxy firewall and out of the firewall(home network)

Steps To Reproduce:

1.Put the break point at line 12, after click the start debugging button(green play),
2.Apex debug session started,
3.in browser enter my apex controller path
4.hit the break point , after i press F10, nothing happens

Expected result

debugger cursor should move to next line and Request Should be Resumed.

Actual result

nothinh happens , request stopped message appears in debug console.

Additional information

Feel free to attach a screenshot.

VS Code Version:
1.20.1

SFDX CLI Version:
sfdx-cli/6.3.0-7600a88 (windows-x64) node-v8.9.4

OS and version:
Windows 7 enterprise SP1

Summary

Trying to install the latest 41.4.0 version of SalesforceDX plugin and getting error to always restart the code

Steps To Reproduce:

1. This is step 1.
   Uninstall current version and try reinstalling the 41.4.0 version

Expected result

Describe what should have happened.

Install DX

Actual result

Installation failed

Additional information

Feel free to attach a screenshot.

VS Code Version:

Version 1.17.2 (1.17.2)

SFDX CLI Version:

sfdx-cli/6.0.9-3391781 (darwin-x64) node-v8.6.0

OS and version:

MAC OS

Summary

ERR_ASSERTION: A name parameter is required to create a storage error message when using SFDX:Create Project

Steps To Reproduce:

1. install java via https://www.digitalocean.com/community/tutorials/how-to-install-java-with-apt-get-on-ubuntu-16-04
2. Install SFDX CLI and salesforcedx-vscode into vscode
3. run use SFDX: create project
4. observe "ERR_ASSERTION: A name parameter is required to create a storage" in bottom console.

Note: running sfdx force:project:create --projectname testing --outputdir /home/neil/playground/salesforce/test in command line gives same error

Expected result

SFDX project should be created

Actual result

Error message in terminal: ERR_ASSERTION: A name parameter is required to create a storage

Additional information

VS Code Version:

Version 1.19.2
Commit 490ef761b76b3f3b3832eff7a588aac891e5fe80
Date 2018-01-10T15:57:21.071Z
Shell 1.7.9
Renderer 58.0.3029.110
Node 7.9.0
Architecture x64

SFDX CLI Version: sfdx-cli/6.0.26-3d23012 (linux-x64) node-v8.6.0

OS and version: Ubuntu 16.04

**Java version: **:
java version "1.8.0_151"
Java(TM) SE Runtime Environment (build 1.8.0_151-b12)
Java HotSpot(TM) 64-Bit Server VM (build 25.151-b12, mixed mode)

Internal Work Item: W-4241831

Summary

It would be brilliant if the Apex, Lightning, and Visualforce Code editor extensions could apply to any Apex classes / Lightning Components / Visualforce pages, regardless of whether they are contained inside an SFDX project.

At the moment, it is possible to sort-of monkeypatch the behavior in by creating a dummy sfdx-project.json file at the root of any other Salesforce project tree.

As the extensions grow and evolve, I fear that this affordance will be lost. This would be a huge loss to a lot of developers who are stuck in a world where porting older, larger, more ungainly projects into DX is impossible/impractical.

Steps To Reproduce:

1. Get a local copy of a Salesforce Org in the non-DX way (e.g. with MavensMate)
2. Add a sample sfdx-project.json to the root of the project (I just copied in the one from dreamhouse and it seemed to work)
3. Open it in VSCode
4. Enjoy wonderful realtime tab completion and syntax highlighting without having to wait for a round trip to the Org to complete

Additional information

Perhaps associating the language sets with certain file extensions would be really useful, so that we could choose / override / configure at a per workspace level within VSCode, rather than having to list folders in the json file?

VS Code Version:
1.16.1

SFDX CLI Version:
sfdx-cli/5.7.6-d42cf65 (windows-amd64) go1.7.5 sfdxstable

OS and version:
Windows 10 Pro

Functionality

A common use case when developing with the Platform is to query existing data. For that the sfdx command to query data via SOQL and output that data should be implemented.

Implementation

• A new menu binding "SFDX: Execute SOQL query" will be implemented.
• User enters the wanted SOQL query into a VScode inputBox.
• SOQL query will be run against the project scratch org, output in JSON format.
• Rendering of the output JSON as HTML in preview side pane (maybe using mustache/handlebars).

As we just discussed, it would be great if I could interact with the language server without having to spin up a separate process and communicate over the network. It looks like I should be able to instantiate the server process in-memory and hand it non-socket-based streams, so that might work, albeit unsupported. It would be great, though, if I could just instantiate the server and then perform direct request/response interactions with it, e.g.:

String diagnosticsRequest = createPublicDiagnosticsRequest();
String diagnosticsResponse = languageServer.sendRequest(diagnosticsRequest);
PublicDiagnostics diagnostics = PublicDiagnostics.create(diagnosticsResponse);
addEditorAnnotations(diagnostics);

Hi,

I am a developer from VS Code team. I am analysing the trend of extension failures reported to our telemetry database when users install/update extensions in VS Code. We use error codes and send them to our telemetry database to understand when an extension is failing while it is being installed. Once understanding the reasons behind the failures, we are fixing in VS Code if there are any thereby making extension installation better.

As part of this, I have seen that the extension salesforce.salesforcedx-vscode-core has high failure rate (53%) recently in vscode insiders (last 7 days). Majority of the failures are coming from when we try to delete the extension folder with the same name+version as the extension being updated.

I would like to know if you are aware any failures or such related failures. It would be great if you can share that information so that we can improve it from our side.

Summary

I'd just like to know if there is a way to authenticate with a trailhead org and learn about it as we learn about the platform.

Steps To Reproduce:

1. Try to auth with trailhead

Expected result

Login with org id or using -r trailhead-url.lightning.salesforce.com

Actual result

No org with that ID

VS Code Version: 1.18

SFDX CLI Version: 6.0.14-2af879b

OS and version: Windows 10 Enterprise, 64 Bit

Summary

I need some guidance on how to use this tool. Are there instructions somewhere on how I can use this tool like I used Mavensmate? I'm looking for a place to put in my Salesforce sandbox credentials (ie. username, password, salesforce sandbox instance name). Any help you can offer would be super helpful.

Summary

The only command showing up when i press F1 is SFDX: Create Project, even though my project has all the necessary files.

What i tried:
Opening the Dreamforce and Simple projects.
Reinstalling the Salesforce extensions.
Reinstalling VSCode
Reinstalling SFDX CLI
Setting up the scratch org through sfdx.exe.

Manually pulling and pushing through sfdx.exe worked as expected.

Steps To Reproduce:

Create a project and open it in VSCode.

Expected result

The full set of SFDX commands available.

Actual result

Can only access "SFDX: Create Project" command.

Additional information

VS Code Version: Stable 1.19.3

Java JDK Version: 8u161

SFDX CLI Version: sfdx-cli/6.1.19-4341549 (windows-x64) node-v8.9.4

OS and version: Windows 10 (16299.192)

Internal Work Item: #W-5171263

Summary

Currently, if a project folder is opened in VS Code that does not contain an sfdx-project.json file none of the SFDX commands are exposed in the Command Palette. This causes confusion for users (like me) who didn't read the instructions which explain this behavior. For example, see this issue. At a minimum users should see an option in the Command Palette to "Initialize Salesforce DX Project" that runs force:project:create and queries the user for the project name. This will greatly reduce confusion and reassure users that the extension is working, but steps are required to use it fully.

Steps To Reproduce:

1. Open a VS Code window pointing to a folder with no sfdx-project.json file
2. Open the command palette and search for "SFDX" commands

Expected result

Users would expect there to be some options available if the SFDX extension is installed

Actual result

'No commands matching' is shown in the Command Palette

Additional information

VS Code Version:
1.17.2

SFDX CLI Version:
sfdx-cli/6.0.14-2af879b (darwin-x64) node-v8.6.0

OS and version:
Mac OS X 10.11.6

Summary

When executing SFDX: Invoke Apex Tests from the VSCode Command bar, the following command is invoked:
sfdx force:apex:test:run --classnames ClassNameTest --resultformat human --synchronous

There is an error ! Unexpected argument --synchronous because --synchronous is not a valid argument.

Steps To Reproduce:

1. Run "Invoke Apex Tests
2. Failure
3. Execute command in shell without --synchronous flag with success.

Expected result

Test for single test class should run successfully.

Actual result

Invalid Argument error.

Additional information

Feel free to attach a screenshot.

VS Code Version: 1.18.1

SFDX CLI Version: sfdx-cli/6.0.14-2af879b

OS and version: Windows 10 1703

Summary

If there is any invalid syntax in the code, it does not show errors on the save but shows errors only when I push the code to the server, using the command "sfdx force:source:push". I was expecting plugin to show at least basic syntax errors on local save.

Steps To Reproduce:

1. Have VScode setup with latest sfdx plugins and pointing to a scratch org.
2. Open any Visualforce and add an invalid attribute. Please see the below screenshot.

Expected result

I was expecting that it would show some kind of alert/error to the user showing the invalid syntax.

Actual result

File saved successfully and no error shown to the user.

Additional information

VS Code Version:
Version 1.17.2

SFDX CLI Version:
sfdx-cli/6.0.13-a52f73c (linux-x64) node-v8.6.0

OS and version:
Ubuntu 16.04 LTS

Summary

There is not any completion for standard components (from lightning namespace) in .cmp file.

Steps To Reproduce:

1. sfdx force:lightning:component:create -n mylightningcomp
2. Open mylightningcomp.cmp file
3. Start typing <lightning: then CTRL+SPACE

Expected result

List of components available in lightning namespace

Actual result

Nothing is proposed

Additional information

I do not find any documentation about this completion, maybe this is just not implemented (yet ?)

VS Code Version:

1.21.1

SFDX CLI Version:

6.8.2

OS and version:

Windows 7

Summary

Hello, I wonder if there is way to open and work with static resources.
Let's say we have a zip static resource with the following structure:
--> my_static_resource
------->css
-----------> my_styles.css
-------> js
-----------> my_app.js
How can I see the actual files and work with them?

Steps To Reproduce:

1. Create a static resource with the structure above.
2. Retrieve the static resource into your project.
3. Try opening the static resource.

Expected result

Unziped static resource.

Actual result

Message: "The file will not be displayed in the editor because it is either binary, very large or uses an unsupported text encoding."

Additional information

Feel free to attach a screenshot.

VS Code Version: 1.21.1

SFDX CLI Version: 42.7.0

OS and version: El Capitan 10.11.6

Summary

Getting this message
"Java runtime could not be located. Set one using the salesforcedx-vscode-apex.java.home VS Code setting"

Steps To Reproduce:

Open visual studio code with the extension enabled

VS Code Version:
1.15.1
SFDX CLI Version:
v40.0
OS and version:
Windows 10 64 bit.

Summary

I have this error when I try to install the extension:

I narrowed it down by checking the dependencies and try to install them first. it seems the problem is related to the Apex Debugger for Visual Studio Code
I'm not behind any proxy
I had to download the extension and install it manually

Steps To Reproduce:

1. Install the extension from VS Code 1.19.3 on mac os

VS Code Version:
1.19.3
SFDX CLI Version:
6.1.19-4341549
OS and version:
OS X 10.13.3

Summary

Intellisense/code completion doesn't find thing like System in a Apex class.

Steps To Reproduce:

1. create and apex class.
2. Add PropertyPageResult r = new PropertyPageResult();
3. Type r.
4. Type System.

Expected result

When typing something like System. I expect to get a list of methods or when typing r. O expect a list of properties

Actual result

No code completion is shown. In other words no properties for r. are shown. No methods shown for System. It doesn't even show 'System'

Additional information

Feel free to attach a screenshot.

VS Code Version:
Version 1.15.1
Commit 41abd21afdf7424c89319ee7cb0445cc6f376959

SFDX CLI Version:
Version 1.15.1
Commit 41abd21afdf7424c89319ee7cb0445cc6f376959

OS and version:
Ubuntu 16.04 LTS

Kind of stupid question. Is apex-jorje-lsp.jar the apex lang server?

Thx

Jay

Summary

I'm using visual studio code, v 1.21.0, I added all SFDX extensions,
I can connect to SF, push code to SF, just can't debug.

I attached the "Launch Apex Debugger

Error - dialog box

Apex language server could not provide information about valid breadpoints

	button --> Open launch.json  button--> Cancel

Steps To Reproduce:

1. Went to debugger tools, and it show multiple JS errors
2. Activating extension failed to load

Expected result

Describe what should have happened.

Actual result

Describe what actually happened instead.

Additional information

Feel free to attach a screenshot.

VS Code Version:

SFDX CLI Version:

OS and version:

Summary

Cannot find the latest version of Java installed on my machine.

Steps To Reproduce:

1. Uninstall any version of Java
2. Navigate to http://www.oracle.com/technetwork/java/javase/downloads/index.html
3. Install the latest version for your OS
4. Launch VS Code

Expected result

VS Code opens without error message.

Actual result

Receive error message: Java 8 is required to run. Download and install it from https://java.com/en/download/.

Additional information

I need Java 9 and am not keen to run versions 8 and 9 side by side.

VS Code Version: 1.18.1

SFDX CLI Version: 6.0.16-3780698

OS and version: macOS 10.13.1

JRE version: build 9+181

Summary

I would expect to be able to use go-to-definition/peak definition on pretty much any symbol (Class Type, class instance methods, variable). However, as far as I can tell it only works on top level class properties and methods when you are inside of the class file.

Steps To Reproduce:

1: Class Types don't work

• Find a reference to a class type eg MyClass myClassInstance = new MyClass();
• Right click on MyClass then select "go-to definition"

2: Instance methods don't work

• Find a method call on an instance method. EG: myClassInstance.fooBar()
• Right click on fooBar then select "go-to definition"

3: Static references don't work

• Find a static property or method reference call on an instance method. EG: MyClass.MY_CONSTANT
• Right click on MY_CONSTANT then select "go-to definition"

Expected result

1: The MyClass file would be opened and the cursor would be put on the class declaration.

2: The MyClass file would be opened and the cursor taken to the declaration of the fooBar method

3: The MyClass file would be opened and the cursor taken to the declaration of MY_CONSTANT

Actual result

No Definition found

Additional information

VS Code Version:
All
SFDX CLI Version:
All
OS and version:
All

Summary

Following the video on https://github.com/forcedotcom/salesforcedx-vscode/wiki. Installing on Windows 10. When I go to open the sfdx-dreamhouse project using code . it opens in VS Code and then get error message

Error: Java runtime could not be located. Set one using the salesforcedx-vscode-apex.java.home VS Code Settings

How do I go about doing that?

Summary

Autocomplete even in Salesforce Apex class is not available.

Steps To Reproduce:

1. Type Http http = new Http();
2. Start typing http.se

Expected result

It should autocomplete with send() method

Actual result

Does not autocomplete any method of Http class

Additional information

It does not happen all the time. Can not reproduce when it is happening.
It is a frequent problem.

VS Code Version:
1.20.1

SFDX CLI Version:
sfdx-cli/6.3.0-7600a88 (darwin-x64) node-v8.9.4

OS and version:
Mac OS 10.13.3

With Java 9 being GA we need to check whether the Apex Language Service supports running with a Java 9 Development Kit.

GPL Binaries (from Oracle) here:
http://jdk.java.net/9

Just Linux for now.

Oracle Java 9 Downloads:
http://www.oracle.com/technetwork/java/javase/downloads/index.html

Summary

Can't install "Lightning Component Code Editor for Visual Studio Code" extension.

Steps To Reproduce:

1. Download the latest VS code editor.
2. Install all extensions one by one as mentioned here "https://marketplace.visualstudio.com/items?itemName=salesforce.salesforcedx-vscode#overview"
3. All extensions are installed except "Lightning Component Code Editor for Visual Studio Code".
4. Received error is "end of central directory record signature not found".

Expected result

Extension should be installed.

Actual result

Received Error.

Additional information

Screenshot attached.

VS Code Version:
1.18.0

SFDX CLI Version:
sfdx-cli/6.0.14-2af879b (windows-x64) node-v8.6.0

OS and version:
Windows 7 , Ulitmate, SP1

Summary

With the frequent usage of the SFDX extension the output command can become quite overloaded. Especially when running multiple commands it's sometimes not that easy to see where the last command started.

Expected result

The output log should be cleared automatically when a new command gets executed. This should be configurable (default: not to clear).

Summary

After installing the extension pack the command palette doesn't provide the options as described in the readme. Tried reinstalling as well as individually installing the extensions.

Steps To Reproduce:

1. Install the extension pack
2. Reload
3. Open an empty folder
4. Open command palette
5. '>SFDX'

Expected result

SFDX options provided by the extension.

Actual result

No commands were found

Additional information

VS Code Version: Version 1.17.0-insider (1.17.0-insider)

SFDX CLI Version: 40.10.0

OS and version: macOS High Sierra 10.13 Beta (17A360a)

Test

The documentation reads that on my mac I should be able to press cmd-shift-o to open an outline of my apex class. Whenever I try that I get the message above.

I installed "salesforce extensions for vs code" as the documentation suggested, and it appears to be active.

Summary

Installed the vscode extension. but not getting the complete set of command and salesforce terminal in output window. Only command it shows is "SFDX: Create project" on running the command. It shows error "No command Found".

Expected result

All ser of commands in sfdx and salesforce terminal in output window

Actual result

only one command "create" that too not running.

Additional information

Feel free to attach a screenshot.

VS Code Version: 1.19.2

SFDX CLI Version:sfdx-cli/6.8.2-f5dd340adc (windows-x64) node-v8.9.4

OS and version: windows 7 enterprise

Summary

Cannot install 40.5.1 (Cannot upgrade Apex extension to 40.5.1)

Steps To Reproduce:

Cannot install 40.5.1

1. Uninstall all current salesforcedx-vscode extension bundle
2. Install salesforcedx-vscode-core
3. The "Install" came back to green status from Grey Blue "Installing" button

Cannot upgrade Apex extension to 40.5.1

1. Install salesforcedx-vscode extension bundle 40.4.0
2. Except for Apex extension, all other salesforcedx-vscode extension bundle members has been upgraded to 40.5.1 automatically.
3. Click green "Install" under salesforcedx-vscode-apex 40.4.0
4. The "Install" came back to green status from Grey Blue "Installing" button, and salesforcedx-vscode-apex remained as 40.4.0

Expected result

Install as 40.5.1 or upgrade to 40.5.1

Actual result

Cannot install 40.5.1
The "Install" came back to green status from Grey Blue "Installing" button

Cannot upgrade Apex extension to 40.5.1
The "Install" came back to green status from Grey Blue "Installing" button, and salesforcedx-vscode-apex remained as 40.4.0

Additional information

VS Code Version: 1.14.2

SFDX CLI Version: 40.5.0, 40.4.0

OS and version: Windows 7 Microsoft Windows [Version 6.1.7601]

Summary

I got "Path must be string. Received undefined" error when attempting to start debugger (green Play button)

Steps To Reproduce:

i followed all the steps using below link
https://marketplace.visualstudio.com/items?itemName=salesforce.salesforcedx-vscode-apex-debugger

here is my Launch.json file:
{ "version": "0.2.0", "configurations": [ { "name": "Launch Apex Debugger", "type": "apex", "request": "launch", "sfdxProject": "${workspaceRoot}" } ] }

Expected result

Debugg session should be start

Actual result

"TypeError:Path must be string. Received undefined" error

Additional information

VS Code Version:
1.20
SFDX CLI Version:
CLI version --- sfdx-cli/6.2.1-9477838 (windows-x64) node-v8.9.4
Apex debugger vscode extension version --- 42.2.0
sfdx force version --- v42.0

OS and version:
Windows 7 enterprise SP1

Summary

When editing a visualforce page, when I comment out a line of javascript, I expect the language service to use the // for javascript, however it is using <!-- -->.

Steps To Reproduce:

1. Open a VF page
2. Add a script tag
3. Add some javascript
4. Use keyboard shortcut to comment out a line of javascript

Expected result

Javascript comments should use //.

Actual result

Javascript is commented out with <!-- -->.

Additional information

Feel free to attach a screenshot.

Extension version: 41.5.0

VS Code Version: 1.17.2

SFDX CLI Version: 6.0.9-3391781

OS and version: OSX 10.12.6

The language server is currently only added to this project as a compiled jar. Please release the source so we can contribute to that functionality. Many things are broken

Summary

running sfdx force:source:status or sfdx force:source:pull and getting error

ERROR: Unexpected file found in package directory: C:\repo\salesforce-food-bank\src\package.xml.

Steps To Reproduce:

1. clone https://github.com/groundwired/salesforce-food-bank
2. Use CumulusCI to deploy
3. Make a change in the scratch org
4. sfdx force:source:status or sfdx force:source:pull

Expected result

to sync back the scratch org change

Actual result

error - above

Additional information

Added package.xml to the .forceignore and then sfdx:source:status works but sfdx force:source:pull generates a different error.

ERROR: version.match is not a function.

looking at C:\Users[myuser].sfdx\sfdx.log

{"name":"sfdx","hostname":"DESKTOP-GBTN6MU","pid":16608,"level":50,"msg":"version.match is not a function.","time":"2017-11-13T01:16:58.721Z","v":0}
{"name":"sfdx","hostname":"DESKTOP-GBTN6MU","pid":16608,"level":50,"msg":"[ false,\n '{"message":"version.match is not a function","status":1,"stack":"TypeError: version.match is not a function\\n at MdapiPackage.setVersion (C:\\\\Users\\\\dboyc\\\\AppData\\\\Local\\\\sfdx\\\\client\\\\node_modules\\\\salesforce-alm\\\\dist\\\\lib\\\\mdapiPackage.js:111:25)\\n at new MdapiPackage

the code there is

/**
* Set the package version
* @param version the version intended to be included in package.xml
/
setVersion(version) {
if (!util.isNullOrUndefined(version)) {
if (version.match(/[0-9].0/)) {
this.Package.version = version;
}
else {
throw almError('invalidVersionString');
}
}
}

There is where it is throwing the version.match is not a function I'm guessing because the version is coming in as null.

Feel free to attach a screenshot.

VS Code Version:
1.18

SFDX CLI Version:
sfdx-cli/6.0.14-2af879b (windows-x64) node-v8.6.0

** CCI Version**:
2.0.0-beta75

OS and version:
Windows 10

Summary

Linter to check for deprecated Lightning Design System class names, such as the deprecated '--' BEM syntax in classes like slds-button--brand. Extension will suggest slds-button_brand instead