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
: is useful to bind a path variable. However, : is a variable character for a path.
If a path variable :foo is mixed with a literal :, it is ambiguous and difficult to know the exact scope of the variable, e.g. /api/v1/:project:get.
Currently, project:get is regarded as a path variable. It makes no sense because I believe most people intend to use project as the path variable and :get is an exact path match.
I don't see that it is inconvenient to only use {project} in a path pattern. Excluding : from path variables and using it only as literals would be a way to eliminate ambiguity and simplify our logic.
Instead, : could be used as a special character within {} to indicate the type of the parameter.
:
is useful to bind a path variable. However,:
is a variable character for a path.If a path variable
:foo
is mixed with a literal:
, it is ambiguous and difficult to know the exact scope of the variable, e.g./api/v1/:project:get
.Currently,
project:get
is regarded as a path variable. It makes no sense because I believe most people intend to useproject
as the path variable and:get
is an exact path match.I don't see that it is inconvenient to only use
{project}
in a path pattern. Excluding:
from path variables and using it only as literals would be a way to eliminate ambiguity and simplify our logic.Instead,
:
could be used as a special character within{}
to indicate the type of the parameter.armeria/core/src/main/java/com/linecorp/armeria/server/ParameterizedPathMapping.java
Line 146 in 2112f50
The text was updated successfully, but these errors were encountered: