-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Navigation Mixin does not work #86
Comments
NavigationMixin is not supported in the local development server. There are some modules the local development server does not support at this point! |
@msrivastav13 where can I open an Issue regarding the other problem of the navigation mixin not working even inside Salesforce? I copied and pasted the example from the docs and it did not work. |
@AllanOricil I suggest you first use a platform like https://salesforce.stackexchange.com/ to post a query on what is not working with the code. You can also open a support case with Salesforce Support! |
Looking at the code you have it wrong, where did you copy the code from? Make sure your class extends NavigationMixin and passes LightningElement as shown below
The above will work in Salesforce org but not in the local dev server as it is not supported yet! |
@msrivastav13 thanks for noticing that |
Description
I opened this issue on the LWC repo, but it seems it belongs to this repo. salesforce/lwc#2073
I tried to use the navigaton example from the official docs, as it is, and it didn't work. On the local development server this example throws an error, while inside salesforce it does not throw anything.
https://developer.salesforce.com/docs/component-library/bundle/lightning-navigation/documentation
Steps to Reproduce
Create a LWC component with a button.
or
Expected Results
It should send the user to the account home page or new page
Actual Results
on Local development server it throws this exception
on Salesforce org it does not throw any error and it does not navigate the user to anywhere.
Browsers Affected
Tested only on Chrome Version 86.0.4240.111 (Official Build) (64-bit)
The text was updated successfully, but these errors were encountered: