Add new App event "page", emitted when a new Page instance is created #640
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
While the App's "ready" and "load" events provide the app's current Page instance when emitted, those events only fire a single time per App instance.
There are a couple scenarios where an App instance can create a new Page instance after initial load:
app.history.refresh()
That means an app can't rely on the "ready" and "load" events to do custom initialization on Page instances.
To allow such customizations, this adds a new "page" event, emitted each time an app creates new Page instances.
Note - this new event is emitted both during server-side rendering, as well as during client-side initialization and page changes.