You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As today, we use an experimental mechanism to provide a dummy-context mechanism. This relies on a magic string value "WireContextEvent" that can be used to dispatch a DOM event from a wire adapter.
This is not longer needed, and should be removed in favor of the formal context mechanism specified here salesforce/lwc-rfcs#6.
The text was updated successfully, but these errors were encountered:
Hi, not sure if related, but if debug mode is turned on, any time you wire the CurrentPageReference you get an error. Here's an example that happens in the lwc-recipes.
Invalid event type "WireContextEvent" dispatched in element .
@jflowers45 no, your specific question was answered here: #1591 (comment), and this issue is pending to be closed as soon as we merge #1459, which should happen in the next few days, with that change, there will be no more WireContextEvent.
As today, we use an experimental mechanism to provide a dummy-context mechanism. This relies on a magic string value
"WireContextEvent"
that can be used to dispatch a DOM event from a wire adapter.This is not longer needed, and should be removed in favor of the formal context mechanism specified here salesforce/lwc-rfcs#6.
The text was updated successfully, but these errors were encountered: