How to think like a Salesforce Lightning Component Developer.
How to Copy your Org’s Existing Code to an SFDX Project
How to disable a lightning:button in Lightning Component
There are a couple of ways to disable the standard <lightning:button />component that is provided by Salesforce. Picking the best way to achieve this will depend on what you are doing, so let’s explore the different ways.
Disabling by default
If you want a button to be disabled by default, the best way to do this is via component attributes using markup.
button.cmp
<aura:component> <lightning:button label="example" onclick="{!c.buttonAction}" disabled="true"/> </aura:component>
Disabling after event with Javascript
In many cases you’ll want to disable the button after it is clicked. You can do that using the event argument passed to controllers.
button.cmp
<aura:component> <lightning:button label="example" onclick="{!c.buttonAction}"/> </aura:component>
buttonController.js
({ buttonAction: function(component,event,helper){ let button = event.getSource(); button.set('v.disabled',true); } })
Disabling with Javascript but no event
And another useful thing to know is how to disable/enable the button without using the event, but still using Javascript. The best way to do that is to use an aura:id .
button.cmp
<aura:component> <lightning:button label="example" onclick="{!c.buttonAction}" aura:id="disablebuttonid"/> </aura:component>
buttonController.js
({ buttonAction: function(component,event,helper){ let button = component.find('disablebuttonid'); button.set('v.disabled',true); } })
Enabling the button
If you want to enable the button, simply just do the same for disabling except pass false instead of true to the examples.
We can help with Lightning Development
Our team at Eigen X has a great deal of experience with Lightning Development on the Salesforce Platform. Feel free to drop us a line: info@eigenx.com or @eigenx.
Commonly Made Mistakes when Testing Software on the Salesforce Platform
A Realistic Approach to Software Testing on the Salesforce Platform
Chances are that if you’ve developed custom code on your org, you have at least 75% code coverage on the Apex portion of that. Because Salesforce requires that to deploy. But that alone is not a testing strategy for your Org. How much testing should you have? What type of testing should you do? What should you test? These questions are often overlooked when it comes to developing software on the Salesforce Platform.
SFDX Quick Tip: Login to a Sandbox Org with the SFDX CLI
By default the SFDX CLI command sfdx force:auth:web:login will not work if you’re trying to login to a sandbox org. This will open up a window to login.salesforce.com . And as we know to login to a sandbox you need to go to test.salesforce.com.
The Solution
Use the -r or --instanceurl flag with your command. This lets you specify the path of the login page you want to authorize from.
So you have sfdx force:auth:web:login -r https://test.salesforce.com