Open
Conversation
…ng with wildcard matching, type definitions & more
…ents more robustly
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Introduce New Context Creation Utility & Enhance Route Handling
This PR makes significant improvements to the request processing and routing mechanisms within Goster. The updates include:
A new utility function to standardize context creation from incoming HTTP requests, ensuring that all context-related initializations (such as setting headers and parsing parameters) are handled in a single modular component.
Enhanced route handling that now supports robust wildcard matching. This allows developers to define catch-all routes and groups more flexibly while automatically parsing dynamic URL parameters.
Introduction and refinement of type definitions across context and routing-related modules. These changes improve code clarity, enforce type safety, and facilitate future middleware integrations.
Together, these changes pave the way for a more flexible, maintainable, and developer-friendly framework.