-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Vue Router ? #13
Comments
IMHO putting a router might restrict an NW.js application. What if you want multiple windows? Would you have a router with multiple routes for every window? (Question applies to all web frameworks tbh) |
I think I'll add it in. A router is just associating what component to display based on a URL. So even if you opened a new window, it could still benefit from that system, like:
Clicking around in either window would update the URL and swap out the component being used. Since the URL's won't be visible to the user or something you could externally link to, routers aren't really needed in desktop apps. However, their approach to organizing views is still a good mental model and one people would be used to, so would still be helpful to have already set up. |
Exactly what I was thinking! Thanks! @ayushmanchhabra I get your point, obviously in some cases, it wont be very usefull, but i think there are other good enough reasons to add routing to this boiler plate |
Didn't even realize this until halfway through, but duh, this boilerplate builds for the web also. So yes, you absolutely would use the URL's in the web build of your app. @Xsmael Can you try out the I still need to fix up the tests before it can be merged. |
Fixed the test, gonna merge/release. |
It's all good sorry for the delay ^^' i think i'm multitasking too much! I had installed the router and went on with the project, so i didn't check back your reply. Thanks for the nice work! |
This is a nice boilerplate, i'm wondering why you didn't add vue router, that would be a perfect combo!
NWJS + Vite + Vue + Pinia + Router + Vitest
The text was updated successfully, but these errors were encountered: