You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the current implementation of wildcards in this repository, the * character is used to match any path, including sub-paths. While this approach is valid, it deviates from the more common convention found in web frameworks, where * typically matches only at the current level of the path. To match sub-paths, developers often use ** or similar symbols.
Problem:
The current wildcard handling can lead to confusion for users who are accustomed to the standard behaviour in web frameworks. It may also result in unexpected matching outcomes.
Suggestion:
I propose improving wildcard handling to align it with common conventions. Specifically:
Use * to match at the current level of the path.
Introduce ** or another suitable symbol to match sub-paths.
Examples:
Current Behaviour: /user/* matches /user/a/b.
Suggested Behaviour: /user/* matches /user/a, and /user/** matches /user/a/b.
This change will make the wildcard behaviour more intuitive and align it with widely accepted practices.
Let me know your thoughts, thanks!
The text was updated successfully, but these errors were encountered:
Description:
Context:
In the current implementation of wildcards in this repository, the
*
character is used to match any path, including sub-paths. While this approach is valid, it deviates from the more common convention found in web frameworks, where*
typically matches only at the current level of the path. To match sub-paths, developers often use**
or similar symbols.Problem:
The current wildcard handling can lead to confusion for users who are accustomed to the standard behaviour in web frameworks. It may also result in unexpected matching outcomes.
Suggestion:
I propose improving wildcard handling to align it with common conventions. Specifically:
*
to match at the current level of the path.**
or another suitable symbol to match sub-paths.Examples:
/user/*
matches/user/a/b
./user/*
matches/user/a
, and/user/**
matches/user/a/b
.This change will make the wildcard behaviour more intuitive and align it with widely accepted practices.
Let me know your thoughts, thanks!
The text was updated successfully, but these errors were encountered: