Hot answers tagged

2

<aura:if isTrue="{isHover}"> Should be: <aura:if isTrue="{!v.isHover}"> Having errors like this in your code may cause the code not to deploy, or cause unexpected behavior even if it does. Testing this in my org, the output is indeed correct once you fix the merge field. Also, all controller events in Aura always receive ...


2

It depends on the job you have, or the job you want. Most new customers won't use Visualforce (most likely), but there are many, many thousands of jobs at companies that have orgs that are 5-10-15+ years old with a large number of Visualforce and other "legacy" code. For example, we have hundreds of Visualforce pages (most that generate PDFs) that ...


1

When you use <aura:component controller="SomeApexClass">, all @AuraEnabled methods in that Apex class are imported into your controller. That means if you have the following Apex: @AuraEnabled public static Data init() { ... And: ({ init: function(component, event, helper) { ... These two methods will be in conflict, and you'll have ...


1

The controller attribute is for Apex controllers only. You do not use the controller attribute to declare a JavaScript controller. The JavaScript controller should be automatically wired to your component: the platform knows they go together because they are part of the component bundle and follow a specific naming pattern (<componentName>Controller.js)...


1

This is due to browser settings. Salesforce are aware of this issue, caused by the fact that Lightning and Classic (including Visualforce pages) URLs actually relate to different domains and that in LEX any Visualforce pages are embedded via iframes in the Lightning page. Most modern browsers now require "same site" cookie origin to allow cookies ...


1

The creation of these files are controlled by the underlying functions (e.g. force:lightning:component:create for LWC and Aura components). These commands always output all the files they're designed to, and there's no documented way to prevent these files from being created. Some alternative options follow. You can commit just the files you want to keep ...


1

You can use a Lightning App. Like a VFP, they are addressable via a URL: https://mydomain.lightning.force.com/my_ns/appName.app Which you write as: <aura:application extends="force:slds"> <c:myLwc /> </aura:application> You can also just add the lightning__AppPage target and and make a full page app if you prefer, though it ...


Only top voted, non community-wiki answers of a minimum length are eligible