Router Functionality with Customizable 404 Page and Clean-Up Mechanism #17
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
skorotkiewicz
changed the title
This was referenced Feb 5, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Customizable 404 Page Support:
Added the ability to configure a custom 404 error page. Users can now specify their own route for handling 404 errors, increasing the framework's flexibility and adaptability to individual needs.
Router Clean-Up Mechanism:
A destroy function for router instances. This function allows for the removal of hashchange event listeners and the cleanup of the router instance from the DOM. This enhancement is particularly useful in SPA applications where dynamism and resource control are essential.
69 lines :)