clone/vikunja
1
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-04-29 00:25:19 +00:00
Code Issues Packages Projects Releases Wiki Activity
12,206 Commits 87 Branches 59 Tags
8a4e43fb96246841b01971f4e4e608f9bcd265f8
Commit Graph

1694 Commits

Author SHA1 Message Date
kolaente
c84b50b3ee fix(labels): trigger task updated for bulk label task update 2024-09-19 08:59:34 +02:00
kolaente
c252c8f0cd fix: reset id before creating 2024-09-17 10:46:14 +02:00
kolaente
6f27e1401a fix(user): do not create user with existing id 
Resolves https://vikunja.sentry.io/share/issue/6f1e37d4b8b248188e20650234a45cde/
 2024-09-14 12:16:05 +02:00
kolaente
1451f6e46f fix(kanban): correctly paginate filtered kanban buckets 
Resolves https://github.com/go-vikunja/vikunja/issues/314
 2024-09-14 09:37:21 +02:00
kolaente
45ff5907e6 fix(view): correctly resolve bucket filter when paginating 2024-09-13 19:45:48 +02:00
kolaente
1a8f12ac13 fix(kanban): do not mark first bucked as done bucket in filter bucket mode 
Resolves https://github.com/go-vikunja/vikunja/issues/313
 2024-09-13 11:52:44 +02:00
Frederick [Bot]
9dd95101f9 [skip ci] Updated swagger docs 2024-09-12 08:42:38 +00:00
kolaente
20724f6fb5 fix(task): cyclomatic complexity 2024-09-12 10:24:16 +02:00
kolaente
8d730543c3 fix(project): reset id before creating 
Resolves https://vikunja.sentry.io/share/issue/6f1e37d4b8b248188e20650234a45cde/
 2024-09-11 23:46:13 +02:00
kolaente
55dd7d2981 fix(task): specify task index when creating multiple tasks at once 
This change allows to specify the task index when creating a task, which will then be checked to avoid duplicates and used. This allows us to calculate the indexes for all tasks beforehand when creating them at once using quick add magic.
The method is not bulletproof, but already fixes a problem where multiple tasks would have the same index when created that way.

Resolves https://community.vikunja.io/t/add-multiple-tasks-at-once/333/16
 2024-09-11 17:58:42 +02:00
kolaente
44a43b9f86 fix(auth): restrict max password length to 72 bytes 
Bcrypt allows a maximum of 72 bytes. This is part of the algorithm and not something we could change in Vikunja. The solution here was to restrict the password during registration to a max length of 72 bytes. In the future, this should be changed to hash passwords with sha512 or similar before hashing them with bcrypt. Because they should also be salted in that case and the added complexity during the migration phase, this was not implemented yet.
The change in this commit only improves the error handling to return an input error instead of a server error when the user enters a password > 72 bytes.

Resolves https://vikunja.sentry.io/share/issue/e8e0b64612d84504942feee002ac498a/
 2024-09-10 18:23:06 +02:00
kolaente
1085a6583b fix(caldav): reject invalid project id with error 400 
Resolves https://vikunja.sentry.io/share/issue/6fc18edefa0e4db3b2e10efe36deeaa4/
 2024-09-10 17:32:35 +02:00
kolaente
e698ac5a34 fix(label): ignore existing ID during creation 2024-09-10 16:45:40 +02:00
Frederick [Bot]
2539f15dfb [skip ci] Updated swagger docs 2024-09-07 11:48:49 +00:00
kolaente
5c1b2846a1 docs(api): use correct return type for the /user endpoint 2024-09-07 13:27:06 +02:00
Frederick [Bot]
2b8515b91d [skip ci] Updated swagger docs 2024-09-06 11:18:51 +00:00
kolaente
68636f27da fix(files): use absolute path everywhere 2024-09-06 12:59:48 +02:00
kolaente
cf94cc8cab chore(docs): clarify usage of related model creation 
Resolves https://github.com/go-vikunja/vikunja/issues/323
 2024-09-06 12:06:12 +02:00
kolaente
02c1de55c4 chore(attachments): refactor building image preview 2024-09-06 09:43:59 +02:00
kolaente
9d7b6d3d9a feat(dump): add flag to allow specifying dump path 
Resolves https://community.vikunja.io/t/vikunja-0-24-docker-bin-sh/2621/3
 2024-09-05 15:14:03 +02:00
kolaente
c2b116de70 chore(files): use absolute file path to retrieve and save files 2024-09-05 15:03:32 +02:00
kolaente
ffcc48ec87 fix(caldav): make sure colors are correctly saved and returned 
Resolves https://community.vikunja.io/t/caldav-sync-tasks-org-strips-colour-and-end-date-values/2753/2
 2024-09-04 23:08:29 +02:00
Frederick [Bot]
5aa0b6a0cf [skip ci] Updated swagger docs 2024-09-04 20:43:53 +00:00
kolaente
b60efbd259 chore(subscription): return subscription entity type using json Marshaler 2024-09-04 22:25:03 +02:00
kolaente
34ac29fcce fix(reminders): notify subscribed users as well 
Resolves https://community.vikunja.io/t/no-reminder-notification-by-e-mail-from-my-colleague/2779
 2024-09-04 22:11:07 +02:00
kolaente
75f3e930cd fix(subscriptions): do not panic when a task does not have a subscription 2024-09-04 21:55:14 +02:00
kolaente
4ff8815fe1 fix(subscriptions): cleanup and simplify fetching subscribers for tasks and projects logic 
Vikunja now uses one recursive CTE and a few optimizations to fetch all subscribers for a task or project. This makes the relevant code easier to maintain and more performant.
 2024-09-04 19:55:17 +02:00
kolaente
115d1c3618 fix(subscription): always return task subscription when subscribed to task and project 2024-09-03 22:37:53 +02:00
kolaente
06305eb6b3 fix(subscriptions): correctly inherit subscriptions 
Resolves https://community.vikunja.io/t/e-mail-notification-twice/2740/20
 2024-09-03 22:04:11 +02:00
kolaente
2c9becec10 fix(notifications): only add project subscription as task subscription when the user is not already subscribed to the task 
Before this fix, a project subscription object was added twice to the list of subscriptions for a task when the user did not subscribe to the task directly. This caused the user to receive a comment notification twice for a given task.
This was probably a regression from efde364224.

Resolves https://community.vikunja.io/t/e-mail-notification-twice/2740/18
 2024-09-02 23:36:58 +02:00
kolaente
5c56d07215 chore(web): always set internal error 2024-09-01 19:37:27 +02:00
kolaente
6fb314b326 chore(web): use logger directly 2024-09-01 19:37:27 +02:00
kolaente
9b01666ec6 chore(web): use web auth factory directly 2024-09-01 19:37:27 +02:00
kolaente
bcfd72c645 chore(web): use config directly 2024-08-29 18:41:20 +02:00
kolaente
499f66b7ae chore(web): directly use new db session 2024-08-29 16:31:46 +02:00
kolaente
8e37d5cb76 chore(web): remove redundant use of fmt.Sprintf 2024-08-29 16:28:37 +02:00
kolaente
57ba073874 chore(web): use errors.As instead of type assertion 2024-08-29 16:28:16 +02:00
kolaente
329de3aab3 chore(web): remove unused echo context 2024-08-29 16:20:39 +02:00
kolaente
74a74b7ec7 fix(labels): test error assertion 2024-08-29 16:16:41 +02:00
kolaente
2063da9eec chore(web): move web handler package to Vikunja 2024-08-29 16:15:28 +02:00
kolaente
7a7e97770c chore(errors): always add internal error to echo error 2024-08-29 15:39:34 +02:00
kolaente
bea131cfd9 fix(labels): trigger task.updated event when removing a label from a task 2024-08-29 15:19:06 +02:00
kolaente
5a0d1f1dc6 feat(event): simplify dispatching task updated event from only a task id 2024-08-29 15:18:03 +02:00
kolaente
efde364224 fix(subscriptions): ignore task subscription when the user is subscribed to the project 
Resolves https://community.vikunja.io/t/e-mail-notification-twice/2740/12
Resolves https://github.com/go-vikunja/vikunja/issues/316
 2024-08-29 10:35:05 +02:00
kolaente
fde1763eef fix(api): return 404 response when using a token and the route does not exist 2024-08-29 10:12:20 +02:00
kolaente
429c7ca2c1 feat(task): always insert new tasks at the top 
Resolves https://community.vikunja.io/t/kanban-cards-in-wrong-order/2731
 2024-08-28 15:30:40 +02:00
kolaente
bf56311faa fix(task): set done at date when moving a task to the done bucket 
Resolves https://github.com/go-vikunja/vikunja/issues/320
 2024-08-28 14:21:31 +02:00
kolaente
8bfd0493b2 fix(deps): update golangci 2024-08-25 14:30:46 +00:00
kolaente
ebfd5f54d2 fix(migration): ensure project background gets exported and imported 2024-08-12 17:18:07 +02:00
kolaente
28b4eaee31 fix(migration): make sure tasks are associated to the correct view and bucket for data imported from Vikunja dump 
This change fixes a bug where imported projects would contain the default views additionally to the ones included in the export. This also caused the tasks to not show up in the views and buckets where they should show up, the newly imported ones.

Resolves https://community.vikunja.io/t/migration-from-vikunja-export-duplicated-boards-local-to-oidc/2690
 2024-08-12 17:00:16 +02:00