Purpose of recommending hash routing

[j-bullard]

What is the purpose behind recommending hash routing with Wails? Are there any drawbacks to using the full URL instead of a hash strategy? I've used both and tested various scenarios and haven't come across a reason why hash would be recommended over the full url.

[kafaa-dev]

At first, I was curious too, and because I've no reason to use hash routing, I used window.location.pathname for routing (browser routing/full URL).

But today, I've encountered this error:

undefined is not an object (evaluating 'window['go']['main']')

The error sometimes occurs after a page reload, for example, when manually reloading or during hot-reloads.

Related issues:

• Runtime and IPC only injected on index.html file #2047 (error occured when accessing HTML files other than index.html)
• Random "TypeError: undefined is not an object (evaluating 'window['go']['backend']')" #2262, Wails runtime object exists only on "/" path url #2741 (error occured every time the app hot-reloads, and other cases)
• [Error] TypeError: undefined is not an object (evaluating 'window['go']['main']') #2710 (error occured after window.location.reload())

The cause is that the Wails Runtime and IPC are only injected when the path ends with /index.html or / (/folder/index.html probably works too) :

wails/v2/pkg/assetserver/assetserver.go

Lines 248 to 255 in 896a90f

	func (AssetServer) isRuntimeInjectionMatch(path string) bool {
	if path == "" {
	path = "/"
	}
	return strings.HasSuffix(path, "/") ||
	strings.HasSuffix(path, "/"+indexHTML)
	}

The solution is either by using in-memory routing, hash routing, or manually inject the Wails IPC and Runtime (https://wails.io/docs/guides/frontend/#script-injection).

Hope this helps.