1
0

10 Commits

Author SHA1 Message Date
Dominik Pschenitschni
23707fc493 feat: eslint enforce vue/component-name-in-template-casing 2024-06-17 21:01:36 +00:00
Dominik Pschenitschni
d1b39ee953
feat(components): align component name casing Message 2024-06-17 13:41:33 +02:00
Dominik Pschenitschni
2004d129c3 feat: reduce eslint warnings (#2396)
Also added `Destructuring the 'props' will cause the value to lose reactivity` as a warning to prepare for the removal of the propsDestructure option in vite.

Reviewed-on: https://kolaente.dev/vikunja/vikunja/pulls/2396
Reviewed-by: konrad <k@knt.li>
Co-authored-by: Dominik Pschenitschni <mail@celement.de>
Co-committed-by: Dominik Pschenitschni <mail@celement.de>
2024-06-17 09:18:02 +00:00
kolaente
0b9ef27d04
fix(migration): show correct message after starting a migration
Related to https://github.com/go-vikunja/vikunja/issues/238
2024-04-07 15:11:59 +02:00
kolaente
89b01e86bc
fix(projects): load all projects when first opening Vikunja 2024-03-02 13:43:04 +01:00
kolaente
178cd8c392
fix: open external migration service in current tab 2024-03-02 11:22:03 +01:00
kolaente
997fb6bc54
fix(migration): show correct help message when a migration was started 2024-02-27 16:36:18 +01:00
kolaente
cc5f48eb74
fix: lint 2024-02-14 14:13:17 +01:00
kolaente
205f330f8a
fix(migration): make sure to correctly check if a migration was already running
This change fixes a bug where Vikunja would not correctly check if a migration was already running. That meant it was not possible for users who had never before migrated anything to start a migration, because Vikunja assumed they already had a migration running for them.
This state was neither properly reflected in the frontend, which is now fixed as well.
2024-02-13 22:21:59 +01:00
kolaente
fc4676315d
chore: move frontend files 2024-02-07 14:56:56 +01:00