using regExp in Path triggers pre, post hooks twice and

[inZaCz]

When using regexp (pattern or in string) in path in route definition. pre and post hooks are trigged twice and also triggered even outside the router basePath when leaving page with router

Example:
{ path: '(?<page>.*)', hooks: { post: [async (route) => { page = route.result?.path?.params?.page; console.log('Page', page); }], }, },

[inZaCz]

it looks it caused when we have our basepath like this : /MainHtml.html#hashFoe
If we have regexp path /^\/(?<page>[^/]+)$/ on router with basePath /MainHtml.html#hashBar
and change hash to #hashFoe, it will correctly redirect, but the macther on router /MainHtml.html#hashBar still check the REGXP pattern as match and ignores the basePath, which triggers hooks that should not be triggered

in route.result.params.page we then have value MainHtml.html#hashFoe

tha main router basePath is just /MainHtml.html to make the hashes work

[inZaCz]

@mateothegreat
I have just realized when trying to debug and fix this that navigating in nested Routers always triggers parent router hooks twice....

{
			path: '#settings',
			component: Settings,
			hooks: {
				pre: [async (route) => {
					console.log('post route', route);
                                       return true; 
				}],
			},
		}

If inside Settings i have Router

<Router
	id="settings"
	basePath={getBasePath('#settings')}
	bind:instance={router}
	routes = {settingsRoutes}
/>

Every routing iside settings Router (#settings/anyRoute), triggers main router hooks twice
no matter if post or pre.

I am trying to debug this hard, but for now i do not know the reason. windows.hashchange event is triggered only once.....