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
Have been using vaadin router in all my recent projects, and pretty happy with it, thanks!
Today, I fail to figure if it is possible to treat the # character (located as the first character of a route parameter), as a character, instead of the hash prefix.
In my use case, i'd like to find the id route param, from all routes after / starting with # or @ (i'm trying to map matrix/element room & user id, which have these two characters as prefix).
{path: '/profile/#:room_id', component: 'page-profile'} # is not getting triggered, even if `#` is escaped in a regex query
{path: '/profile/@:user_id', component: 'page-profile'} # is getting triggered correctly
expected result
in the case example.com/profile/#matrix:matrix.org where room id is #matrix:matrix.org, the route param id, would have the values #matrix:matrix.org
or in the case example.com/profile/@test-user:matrix.org, where a user id is @test-user:matrix.org, the route param user_id would have the value @test-user:matrix.org
The text was updated successfully, but these errors were encountered:
Hello,
Have been using vaadin router in all my recent projects, and pretty happy with it, thanks!
Today, I fail to figure if it is possible to treat the
#
character (located as the first character of a route parameter), as a character, instead of thehash
prefix.In my use case, i'd like to find the
id
route param, from all routes after/
starting with#
or@
(i'm trying to map matrix/elementroom
&user
id, which have these two characters as prefix).Links:
test 1
It works if
id
starts with@
, but not with#
test 2
expected result
#matrix:matrix.org
, the route paramid
, would have the values#matrix:matrix.org
or in the case example.com/profile/@test-user:matrix.org, where a user id is
@test-user:matrix.org
, the route paramuser_id
would have the value@test-user:matrix.org
The text was updated successfully, but these errors were encountered: