lwc | Blazing Fast , Enterprise-Grade Web Components Foundation | Web Framework library

It's worse than you think. runJob({param2, param1}) will work correctly too. "Correctly" meaning their names matter, not the position!

Your stuff is always passed as an object, not a list of parameters. You could have a helper Apex wrapper class and (assuming all fields are @AuraEnabled) it'll map them correctly. If you have list of parameters - well, a kind of unboxing and type matching happens even before your code is called. If you passed "abc" to a Date variable - a JSON deserialization error is thrown even before your code runs, you have no means to catch it.

https://developer.salesforce.com/docs/component-library/documentation/en/lwc/lwc.apex_wire_method

If the Apex method is overloaded, the choice of what method to call is non-deterministic (effectively random), and the parameters passed may cause errors now or in the future. Don't overload @AuraEnabled Apex methods.

So... pick different names? Or funnel them so the 3-param version looks at the last param and calls 2-param one if needed and the business logic allows it. Generally - keep it simple, leave some comments and good unit tests or 2 months from now poor maintenance guy will struggle.

And (if you use the Apex PMD plugin and/or sfdx scanner) functions with long parameter lists are frowned upon anyway: https://pmd.github.io/latest/pmd_rules_apex_design.html#excessiveparameterlist

See also

• https://github.com/trailheadapps/lwc-recipes/issues/196
• https://salesforce.stackexchange.com/questions/359728/apex-method-overloading-is-not-working-when-called-from-lwc-javascript-controlle

Your organisation is using a "Site" or "Experience Cloud" (formerly known as Customer / Partner Community, formerly known as Customer / Partner Portal). Go to Setup -> Sites or Setup -> Experience... and have a look.

If you had no idea you're using a community there's a chance you don't have real community users & licences (cheaper than regular licenses but still), you might have just the "guest user" for unauthenticated access. Be careful what you expose to guest users

There might be some trailheads and videos if you're lost.

1. Go to community builder and create new page for your component (but don't add the component yet, maybe add just some plain text). The page editor is similar but not identical to "Lightning App Builder" editor. This is the part where you choose "self", "opt-out" etc.
2. Maybe add your page to Navigation Menu at top of the page.
3. Hit "Publish" and check if you can see the new page.
4. Compare your component's "meta.xml" file with the other two. You'll need to add a target (probably lightningCommunity__Page) to it to indicate it's OK to drop it on community page. Deploy.
5. If your component uses Apex - you need to grant permission to run this class to the guest user (or normal community users, if it turns out you actually have them). Guest user is still a Profile, you have all the normal checkboxes - but it's bit hidden. Steps depend whether you have a Site or community.
6. You're ready to go back to your page, drop your component on it and hit Publish again.
7. If you think there are apex errors - debugging guest users is bit of a pain too. Go to Setup -> Debug logs and search users with "guest" in name. Something like "{your community name} Site Guest User" should pop up.

If the server is running, close it by hitting Ctrl+C.

I strongly recommend uninstalling any global installations of ESLint.
To see what global packages are installed, in the command line run: ¹

1. Your component loads to the page and the @wire is called.
2. The component doesn't wait for @wire to finish, it'll be done when it'll be done, asynchronous. Your component carries on.
3. It encounters the html rendering, calls your getter. Well, the variable is undefined/null at that point, @wire didn't return yet. The code tries to do null.data and throws because null/undefined doesn't have fields.
4. Boom, headshot.

Put some null checking in the getter or use the ?. operator

In general, the local development for Lightning Web Components still has beta status: Local Development (Beta)

However, even the beta version can now be used relatively reliably. To set up local development you only need to authorize an org and install the development server. This allows you to develop locally without the need to push your components to an org first.

The local development server and its configuration are provided by a Salesforce CLI plugin. Before you install the plugin make sure you are using the latest Salesforce CLI version by running:

Having a javascript object, you can go through the keys of the object and combine some of them into strings

It will look something like this:

It's the cache issue.

Salesforce does persistent browser caching to improve performance and to load the application faster.

If you want you can disable the caching as follows:

1. Setup.
2. Session Settings.
3. Find Caching settings section on the page.
4. Uncheck Enable secure and persistent browser caching to improve performance.

Do you have a Community... sorry, Experience Builder page with that target LWC dropped?

You could use NavigationMixin although documentation says communities don't support the state property.

On source side try something like