96884372b4
Previously these store methods created multiple edits on deep objects in the store or edited a deep nested object directly. This is bad because: - multiple edits lead to multiple triggers of all the watchers on the project. - in theory we should listen deep to a project if we use some deep reactive value of a project, if we want deep updates. Because this is easy to forget, it's better to update the project directly. For this the method `setProject` already existed in the store. This is no real overhead because Vue is smart enough to only trigger listeners that use data of the modified state. By modifying only a copy of the view and submitting the modified result __once__ we can save us a lot of headache. PS: I'm not sure if there were any visible problems, because Vue is really fast and the reactivity system works quite well. Regardless of this we should try not to modify state unnecessarily. (cherry picked from commit 1e632397d29e9d45609b9271e00111c0a6cb2c57)
Web frontend for Vikunja
The todo app to organize your life.
This is the web frontend for Vikunja, written in Vue.js.
Take a look at our roadmap (hosted on Vikunja!) for a list of things we're currently working on!
Security Reports
If you find any security-related issues you don't want to disclose publicly, please use the contact information on our website.
Docker
There is a docker image available with support for http/2 and aggressive caching enabled. In order to build it from sources run the command below. (Docker >= v19.03)
export DOCKER_BUILDKIT=1
docker build -t vikunja/frontend .
Refer to multi-platform documentation in order to build for different platforms.
Project setup
pnpm install
Compiles and hot-reloads for development
pnpm run serve
Compiles and minifies for production
pnpm run build
Lints and fixes files
pnpm run lint