New feature: Data Store(before PR)

[hezedu]

What problem does this feature solve?

#3445: vue-router positionStore memory leak

reconstruct util/state-key

used window.performance.now() as the state key will reset when localtion reload, It may conflict with other hisotories

What does the proposed API look like?

router.setData(key, data)

• key string
• data any

router.getData(key)

• key string
• Returns: any

router.removeData(key)

• key string

Online Demo:

https://hezedu.github.io/SomethingBoring/vue-router-positionstore-memory-leak/pr-demo.html#/

Why adding these new features?

Unlike window.history, vue-router has no API to change history.state.

But sometimes we need it to store some unique keys, like the positionStore.

So I replaced positionStore with dataStore. This way you can store more things.

And there is no need to develop state related APIs in the future.

[posva]

That's a cool demo! Unfortunately, the router won't have an api to hold state like history.state, it has been discussed many times in different issues and in different routers.

The thing you are trying to improve in v3 is already improved in v4 by using history.state for both HTML5 history and hash history but that won't be possible in v3

The isPop is something that I plan on introducing through an RFC for Vue Router 4. It might be backported to v3 after that

[hezedu]

isPop I have already cut off. Because I can distinguish back , forword, repalce or push in more detail.
This will be another PR (if this PR passes)

[posva]

Closing in favor of #3453 although it still needs to go through an RFC