Add Router.withNotFound to handle unknown URL #320
Merged
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.
Fixes #308.
Example use:
This will send the message
PageChanged NotFound
It does not change the behavior when the user clicks a link to a URL that can't be parsed: these are considered external links, and standard navigation is performed.
Breaking changes
IRouter<'model, 'msg>
has an additional propertyNotFound: 'msg option
.Router<'endpoint, 'model, 'msg>
hasmakeMessage: 'endpoint -> 'msg
;notFound: 'endpoint option
;setRoute
has changed tostring -> 'endpoint option
instead ofstring -> 'msg option
.These should be transparent for most users.