trailheadapps / visualforce-to-lwc Goto Github PK

There are no step titles in CodeTour. Let's add some for a more user-friendly learning experience.
Simply add a title property on each step of your code tours.

Hi,
I'm installing it in a Developer org, I followed the instructions - this is the error that I get when deploying.
Any idea of how to solve it?
Thanks,
Kind regards,
David

davidsanchezcarmona@Davids-MacBook-Air visualforce-to-lwc % sfdx force:source:deploy -p force-app

Job ID | 0Af0H00000jZ3x8SAC
SOURCE PROGRESS | ██████████████████████████████░░░░░░░░░░ | 113/153 Components
TYPE PROJECT PATH PROBLEM
───── ────────────────────────────────────────────────────────────────────────── ─────────────────────────────────────────────────────────────────────────────────────────
Error force-app/main/default/classes/TestCreateMixedRecordsApexControllerLwc.cls Method does not exist or incorrect signature: void startTest() from the type test (6:14)
Error force-app/main/default/classes/TestCreateMixedRecordsApexControllerLwc.cls Method does not exist or incorrect signature: void stopTest() from the type test (12:14)
Error force-app/main/default/classes/TestCreateMixedRecordsApexControllerLwc.cls Method does not exist or incorrect signature: void startTest() from the type test (51:18)
Error force-app/main/default/classes/TestCreateMixedRecordsApexControllerLwc.cls Method does not exist or incorrect signature: void stopTest() from the type test (57:18)
Error force-app/main/default/classes/TestCreateRecordPrepopulatedController.cls Method does not exist or incorrect signature: void startTest() from the type test (13:14)
Error force-app/main/default/classes/TestCreateRecordPrepopulatedController.cls Method does not exist or incorrect signature: void stopTest() from the type test (17:14)
Error force-app/main/default/classes/TestListControllerLwc.cls Method does not exist or incorrect signature: void startTest() from the type test (14:14)
Error force-app/main/default/classes/TestListControllerLwc.cls Method does not exist or incorrect signature: void stopTest() from the type test (16:14)
Error force-app/main/default/classes/TestListWithParentRecordDataCtrllerLwc.cls Method does not exist or incorrect signature: void startTest() from the type test (13:14)
Error force-app/main/default/classes/TestListWithParentRecordDataCtrllerLwc.cls Method does not exist or incorrect signature: void stopTest() from the type test (15:14)
Error force-app/main/default/classes/TestPageMessagesController.cls Method does not exist or incorrect signature: void startTest() from the type test (9:14)
Error force-app/main/default/classes/TestPageMessagesController.cls Method does not exist or incorrect signature: void stopTest() from the type test (11:14)
Error force-app/main/default/classes/TestPageMessagesControllerLwc.cls Method does not exist or incorrect signature: void startTest() from the type test (7:18)
Error force-app/main/default/classes/TestPageMessagesControllerLwc.cls Method does not exist or incorrect signature: void stopTest() from the type test (9:18)
Error force-app/main/default/classes/TestPageMessagesDataRetrievalController.cls Method does not exist or incorrect signature: void startTest() from the type test (9:14)
Error force-app/main/default/classes/TestPageMessagesDataRetrievalController.cls Method does not exist or incorrect signature: void stopTest() from the type test (11:14)
Error force-app/main/default/classes/TestPageMessagesDataRetrievalCtrllerLwc.cls Method does not exist or incorrect signature: void startTest() from the type test (7:18)
Error force-app/main/default/classes/TestPageMessagesDataRetrievalCtrllerLwc.cls Method does not exist or incorrect signature: void stopTest() from the type test (9:18)
Error force-app/main/default/classes/TestPageMessagesFormController.cls Method does not exist or incorrect signature: void startTest() from the type test (9:14)
Error force-app/main/default/classes/TestPageMessagesFormController.cls Method does not exist or incorrect signature: void stopTest() from the type test (11:14)
Error force-app/main/default/classes/TestPageMessagesFormController.cls Method does not exist or incorrect signature: void startTest() from the type test (37:14)
Error force-app/main/default/classes/TestPageMessagesFormController.cls Method does not exist or incorrect signature: void stopTest() from the type test (39:14)
Error force-app/main/default/classes/TestPageMessagesFormControllerLwc.cls Method does not exist or incorrect signature: void startTest() from the type test (7:18)
Error force-app/main/default/classes/TestPageMessagesFormControllerLwc.cls Method does not exist or incorrect signature: void stopTest() from the type test (9:18)
Error force-app/main/default/classes/TestPaginatedListController.cls Method does not exist or incorrect signature: void startTest() from the type test (11:14)
Error force-app/main/default/classes/TestPaginatedListController.cls Method does not exist or incorrect signature: void stopTest() from the type test (15:14)
Error force-app/main/default/classes/TestPaginatedListControllerLwc.cls Method does not exist or incorrect signature: void startTest() from the type test (13:14)
Error force-app/main/default/classes/TestPaginatedListControllerLwc.cls Method does not exist or incorrect signature: void stopTest() from the type test (18:14)
Error force-app/main/default/classes/TestPaginatedListControllerLwc.cls Method does not exist or incorrect signature: void startTest() from the type test (53:14)
Error force-app/main/default/classes/TestPaginatedListControllerLwc.cls Method does not exist or incorrect signature: void stopTest() from the type test (58:14)
Error force-app/main/default/classes/TestRecordPagesController.cls Method does not exist or incorrect signature: void startTest() from the type test (10:14)
Error force-app/main/default/classes/TestRecordPagesController.cls Method does not exist or incorrect signature: void stopTest() from the type test (12:14)
Error force-app/main/default/classes/TestRecordPagesController.cls Method does not exist or incorrect signature: void startTest() from the type test (28:14)
Error force-app/main/default/classes/TestRecordPagesController.cls Method does not exist or incorrect signature: void stopTest() from the type test (30:14)
Error force-app/main/default/classes/TestViewRelatedRecordsController.cls Method does not exist or incorrect signature: void startTest() from the type test (26:14)
Error force-app/main/default/classes/TestViewRelatedRecordsController.cls Method does not exist or incorrect signature: void stopTest() from the type test (28:14)
Error force-app/main/default/classes/TestViewRelatedRecordsControllerLwc.cls Method does not exist or incorrect signature: void startTest() from the type test (19:14)
Error force-app/main/default/classes/TestViewRelatedRecordsControllerLwc.cls Method does not exist or incorrect signature: void stopTest() from the type test (23:14)
Error force-app/main/default/classes/TestCreateMixedRecordsApexController.cls Method does not exist or incorrect signature: void startTest() from the type test (9:14)
Error force-app/main/default/classes/TestCreateMixedRecordsApexController.cls Method does not exist or incorrect signature: void stopTest() from the type test (11:14)
ERROR running force:source:deploy: Deploy failed.

Summary

When wanting to deploy source to org, I get this error message :

lwc/navigateToRecord/navigateToRecord.js-meta.xml: This component doesn't support any target for flows, but it's referenced in these flow versions: 'Create Property-1'. Add any of these targets to the component: 'lightning__FlowScreen'. 
lwc/navigateToRecord/navigateToRecord.js-meta.xml: You can’t change the isExposed property to ‘false’ because the component is part of a managed package.
lwc/navigateToRecord/navigateToRecord.js-meta.xml: This component doesn't support any target for flows, but it's referenced in these flow versions: 'Create Property-1'. Add any of these targets to the component: 'lightning__FlowScreen'. 
lwc/navigateToRecord/navigateToRecord.js-meta.xml: You can’t change the isExposed property to ‘false’ because the component is part of a managed package.

Config:
"path": "force-app",
"default": true,
"package": "vf2lwc",
"versionName": "Spring '22",
"versionNumber": "54.0.0.NEXT"

Salesforce Org Type

Trailhead Playground

Steps To Reproduce

No response

Current Behavior

No response

Expected Behavior

No response

Relevant Log Output

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

Summary

The readme file says there is another permission set named "Walkthroughs". I could not find them anywhere.

Steps To Reproduce:

1. Read Read me file
2. Fix if needed

Expected result

Describe what should have happened.

Actual result

Describe what actually happened instead.

Additional information

Feel free to attach a screenshot or code snippets.

Summary

Hi!

It’s Gleb from Catchpoint.com.

I've noticed that your website links to our old blog, which we’re currently migrating from a subdomain to the main domain. The reason I’m reaching out is to make sure you won’t have a 404 error on your website.

You have a link to our old blog on the following pages:
https://developer.salesforce.com/index.php?title=Network_Best_Practices_for_Salesforce_Architects&oldid=94091
I wonder if you’d be able to replace it with the new one:
https://www.catchpoint.com/blog/tcp-rtt
Thanks for linking to Catchpoint.com!

Please don’t hesitate to contact me if something comes up [email protected]!

Best,
Gleb

Suggested Solution

No response

Alternative Solutions

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

The listRecordLinks LWC doesn't open a record. This is easily recreated by simply clicking one of the account names on the component.

To fix it, the navigate component in navigateToRecord.js should be adjusted from:
import { LightningElement, api } from 'lwc';
import { NavigationMixin } from 'lightning/navigation';

export default class NavigateToRecord extends NavigationMixin(
LightningElement
) {
@api recordId;
@api label;

navigate() {
    this[NavigationMixin.Navigate]({
        type: 'standard__recordPage',
        attributes: {
            recordId: this.recordId,
            actionName: 'view'
        }
    });
}

}

To:
import { LightningElement, api } from 'lwc';
import { NavigationMixin } from 'lightning/navigation';

export default class NavigateToRecord extends NavigationMixin(
LightningElement
) {
@api recordId;
@api label;

navigate(e) {
    e.preventDefault();
    this[NavigationMixin.Navigate]({
        type: 'standard__recordPage',
        attributes: {
            recordId: this.recordId,
            actionName: 'view'
        }
    });
}

}

In summary, without e.preventDefault(), the tag's default navigation takes effect instead of the onclick handler's.

My Domain is now auto activated in new DE orgs.
Let's remove that step from install instructions.

Jest LWC benefits from a wire protocol reform that requires some test code changes.
See this PR for a practical example.