Nothing world changing. I realised recently that I prefer explicitly calling methods of stores and do the same with their states. Similar to how one would do that with classes. Since I might make more changes like this in the future (maybe also part of other PRs) I though I'd explain my reasoning here in a bit more detail: __Benefits__ - saves local mappings, like the `const updateConfig = () => configStore.update()` - there is no need to look up what exactly is updated, since the function is provide by the store. __Disadvantages__ - a little bit more verbose (but not thaaat big difference) --- TLDR: When reading the code this saves the step to check what was mapped. Reviewed-on: https://kolaente.dev/vikunja/vikunja/pulls/2945 Reviewed-by: konrad <k@knt.li> Co-authored-by: Dominik Pschenitschni <mail@celement.de> Co-committed-by: Dominik Pschenitschni <mail@celement.de> |
||
|---|---|---|
| .github | ||
| .vscode | ||
| build | ||
| desktop | ||
| frontend | ||
| pkg | ||
| rest | ||
| .dockerignore | ||
| .drone.yml | ||
| .editorconfig | ||
| .envrc | ||
| .gitignore | ||
| .golangci.yml | ||
| CHANGELOG.md | ||
| CONTRIBUTING.md | ||
| Dockerfile | ||
| LICENSE | ||
| README.md | ||
| cliff.toml | ||
| code-header-template.txt | ||
| config-raw.json | ||
| devenv.lock | ||
| devenv.nix | ||
| devenv.yaml | ||
| go.mod | ||
| go.sum | ||
| magefile.go | ||
| main.go | ||
| nfpm.yaml | ||
| publiccode.yml | ||
| renovate.json | ||
| tools.go | ||
| tsconfig.json | ||
| vikunja.service | ||
README.md
Vikunja
The Todo-app to organize your life.
If Vikunja is useful to you, please consider buying me a coffee, sponsoring me on GitHub or buying a sticker pack. I'm also offering a hosted version of Vikunja if you want a hassle-free solution for yourself or your team.
Table of contents
Security Reports
If you find any security-related issues you don't want to disclose publicly, please use the contact information on our website.
Features
See the features page on our website for a more exhaustive list or try it on try.vikunja.io!
Docs
All docs can be found on the Vikunja home page.
Roadmap
See the roadmap (hosted on Vikunja!) for more!
Contributing
Please check out the contribuition guidelines on the website.
License
This project is licensed under the AGPLv3 License. See the LICENSE file for the full license text.