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
I'm probably going to be using Go-App in an unorthodox way by not encouraging my audience to install the PWA and instead just running it directly in the browser. That aside, I'd like to be able to use the url to persist state between pages allowing my users to link directly to specific pages. I'd love it if it was with path parameters, but I'm okay with just query parameters, but I can't figure out how to extract even the current url in the component. Do I need to call JS to get the current url? I've seen it mentioned a couple of times in other issues that some have implemented their own router sortof that allows for parameters in the path. I'd love it if somebody can share their implementations, even if they're dumped down ones.
The text was updated successfully, but these errors were encountered:
We use JS to get and set the hash of the URL instead of changing the URL itself.
But for returning users we actually prefer using session data. You do not need to have them install the PWA for any of its functionality. It does not make a lot of difference. The main difference in my eyes is the screen real-estate and them having a nice "button" for the app.
I'm probably going to be using Go-App in an unorthodox way by not encouraging my audience to install the PWA and instead just running it directly in the browser. That aside, I'd like to be able to use the url to persist state between pages allowing my users to link directly to specific pages. I'd love it if it was with path parameters, but I'm okay with just query parameters, but I can't figure out how to extract even the current url in the component. Do I need to call JS to get the current url? I've seen it mentioned a couple of times in other issues that some have implemented their own router sortof that allows for parameters in the path. I'd love it if somebody can share their implementations, even if they're dumped down ones.
The text was updated successfully, but these errors were encountered: