Comments (1)
Interesting idea! It does sound like you could use the hash history. Note that you can still store other data with a virtual hash property. You do lose the CSS :target
property as a tradeoff.
You mention 3 other advantages, but the first two apply to the hash history as well, and the last one isn't a concern in a web extension.
In any case, this can be built as a standalone library outside of vue-router (that was one of the advantages of extracting the histories 😄). I don't think this kind of history should be included in vue router because I wouldn't recommend it over the other histories (for the reasons mentioned above), but I would love to see it as a standalone open-source library! It shouldn't be too hard by copying an existing history and replacing the way it handles the path, so you should definitely give it a try. FYI: I offer consultancy for anybody needing help with their products
from router.
Related Issues (20)
- External Type Declaration Causing Inability to Pass certain Route Parameter as Prop in Vue Router 4 HOT 1
- Error: Missing required param HOT 2
- Introduce `elementTargetClass` option (alternative to `:target`) HOT 5
- Introduce `passive` option for `router.push`/`router.replace` HOT 1
- Docs: Close button (to close the ad banner) is hidden HOT 1
- What should I do if I want to use vue-router through cdn in my website?
- CSS Empty on 404 HOT 2
- AddRoute() with ParentName does not add routes as Children of the parent.
- Router has modified my params HOT 1
- Getting syntax errors while using Vite with vue3/router4 HOT 1
- vite + [email protected] 命名视图无法使用 HOT 1
- Under certain conditions, its possible to render the `router.back()` & `history.back()` ineffective.
- await doesn't work for router.go() but does for router.push()? HOT 1
- transition with a comment, new page will not appear HOT 1
- Feature request: have active-class behave like class on router-link HOT 3
- [Vue Router warn]: Finding ancestor route "/:path(.*)*" failed for "/:path(.*)*" HOT 2
- @4.3.3 the redirect / to home is not effective when children get /:pathMatch(.*) HOT 2
- $route, $router, useRoute and useRouter not accessible in child routes of the base route.
- Vue3, Router4 problem HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from router.