Feat/#24 make uri parser flexible support standard schemes #28
+40
−22
Conversation
This file contains hidden or 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
…ization to accept custom URI parser
angryPodo
added
the
FEAT✨
angryPodo
deleted the
feat/#24-make-uri-parser-flexible-support-standard-schemes
branch
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.
Refactored parsing logic to support standard URI schemes (e.g., myapp://home/product?id=123).
DefaultWispUriParser: Removed legacy ?stack= parameter support. Now splits uri.path by a delimiter (default /) to determine the backstack.Wisp.kt: Now extracts all query parameters from the URI and passes them to every route factory. This allows standard query parameters (like ?id=123) to be used across the entire backstack.