https://github.com/mitchspano/lwcrefreshdemo
https://github.com/mitchspano/lwcrefreshdemo
Last synced: about 1 month ago
JSON representation
- Host: GitHub
- URL: https://github.com/mitchspano/lwcrefreshdemo
- Owner: mitchspano
- Created: 2019-11-25T20:58:06.000Z (over 5 years ago)
- Default Branch: master
- Last Pushed: 2020-04-21T05:02:16.000Z (about 5 years ago)
- Last Synced: 2025-03-25T13:11:20.320Z (2 months ago)
- Language: JavaScript
- Size: 1.86 MB
- Stars: 5
- Watchers: 3
- Forks: 8
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# LWC Refresh Demo
This project is meant to illustrate how to broker communications across all Aura and Lightning Web Components within the context of lightning pages. The classic example of this is the 'e.force:refreshView' event, but in theory this could be used to broker all communications between Aura application events and Lightning Web Components.
It is important to note that this solution will allow developers to allow for all components on the page (Aura or LWC) to be refreshed at the same time, no matter if the component initiating the refresh is Aura or LWC.
### Simple Demonstration
Here is a simple demonstration of a Lightning Web Component called accountEditor listening for refreshes from other components, as well as initializing the refresh.
Note the chrome console log statements:
* The accountEditor will log 'Listening to Refresh for LWC' when another component fires the Aura e.force:refreshView event
* The accountEditor will log 'Calling Refresh from LWC' when it is initializing the refresh itself
### Sequence Diagrams
There are two basic flows for brokering in this way:
##### Aura Initiated
##### LWC Initiated
### Adding Components to Lightning Page
This approach will only work if the brokerAura component is somewhere (location does not matter and the markup is empty, so nothing will be visible) on the Lightning page.
In this example, I have placed it above the highlights panel.
