Jakob Rosenberg

Hi @ivmisnik . can I ask what you get if you `console.log(page)`? It seems `npm run build:typings` might be able to fix this.

There's currently no functionality for remembering scroll positions in history. Scroll lock has a different purpose. It prevents the whole page from scrolling to the top, which you sometimes need...

> Hum, understood. What is a good workaround? I'm thinking in save the current position in a store with BeforeURLChange and set it with AfterPageLoad, or is better to use...

Hi @Rican7, moving $isChangingPage would be a breaking change. The helper only shows when a page is actually changing, not when it is loading. There are a few ways this...

I really like your solution. 😄 Any ideas for what a new helper should look like? ```javascript $: isLoading = $isLoadingPage || $isChangingPage ``` or just ```javascript $: isLoading =...

Much agree. Would you be interested in doing a PR? (idea no 1 posted above) I can also do it, but I might not have time till next weekend.

Currently route nodes are either static or parameterized. That's not to say flexibility can't be added to the nodes, just that I haven't come across a justifying use case.

I'd like to support artificial paths. This is an issue I come across myself from time to time. Not sure what the best syntax would be for the following examples....

I thought `|` pipes were illegal characters, but I could easily be wrong.

I'm not sure where else to address how filenames should be parsed. Any aspect affected by a solution should be considered. Please note, I'm not campaigning for magic slashes, just...