That makes sense. Though I think I might do /user/{name} if we add public profile pages (and /me for the logged in user)
Ah, you raise a good point there. It was originally intended to, but then I changed it so that only the events update the state. Thanks for that.
It seems to support a UUID column type, but I don't see documentation for it, or for using it as a primary key. Is that important?
From the Vue docs:
This also means any component importing store can mutate it however…
It's been a while since I looked into it, but I think I remember reading something in their docs which suggested that they might be overkill for this situation.
f32a188750
Merge pull request 'Frontend was merged prematurely, this fixes that' (#3) from frontend/feature/login-view into feature/user-auth
3dbe2d2327
Merge pull request 'Backend feature: user auth' (#1) from backend/feature/user-auth into feature/user-auth
Oh, one thing, I think a lot of this might be simplified by creating a template repo rather than relying too much on documentation. E.G. putting placeholder README, LICENSE, .gitignore, etc.
There could be another section that states how to fork from the CLI
As far as I'm aware this is not possible. The issue I had isn't with using the web UI for the fork button, it was the idea…