New answers tagged

0

I was facing the same issue, but then I tried below and got solved. Go to -> sfdx-project.json file in your vs code Add "oauthLocalPort" : 1717 This worked for me just now.


1

@Vinay thanks for pointing me to that. It is a new feature that is causing it. In the settings there is a new feature that needs to be disabled and that fixed it for me. In Settings: Salesforcedx-vscode-core > Experimental: Use Apex Library Disable - Use Apex Library for Apex CLI Commands


5

There is a current regression bug in the Salesforce CLI latest version causing the issue. For now, you can work around by running below in your vscode terminal sfdx auth:web:login --setalias DevOrg --instanceurl https://login.salesforce.com --setdefaultusername Notice that now you need to use sfdx auth:web:login instead of sfdx force:auth:web:login for ...


0

It is possible to not run tests if you covert to metadata first: sfdx force:source:convert -r force-app -d deploy Then you can deploy the resulting directory deploy: sfdx force:mdapi:deploy -d deploy -w -1 --verbose


0

I also wanted to accomplish this task. I just looked through the source code of sfdx, and it is relatively easy to understand. If you look at the repo on github here: forcedotcom/salesforcedx-templates You can see that src/generators/projectGenerator.ts has the code for generating out the files and folder structure when you create a new template. The files ...


1

This is resolved. The issue in my case was there were certain policies that my company had set in my system that was blocking the execution of those commands.


5

I don't believe there's a GUI option for this (yet?), but you can always just open a Terminal and type in: sfdx force:apex:test:run -s "SuiteName" -c --json Or, you could add it as an npm script in package.json and use the "npm: run task" menu option. For example: { "scripts": { "run-package-tests": "sfdx ...


0

SFDX supports the command: sfdx force:apex:test:run --targetusername thealias I would think that you can run this within VSCode (though I don't use VSCode so can't be 100% sure). Check the documentation for other options.


4

As the warning says, your .forceignore file is not adhering to the .gitignore format. The recent release of CLI recommends (for now it's a warning but looks like from Spring 21 that's the expected format) that you keep your .forceignore following the standards similar .gitignore. This is documented here So you will need to do the below changes so in any ...


0

It gets a squiggle line under getParameters() and a message "Method does not exist or incorrect signature: void getParameters() from the type System.Pagereference" This looks like a bug. This method definitely exists and has not been removed recently. In another language I would think I'm missing a library reference or something but there is no ...


Top 50 recent answers are included