feat: allow marking a related task done directly from the list of related tasks #2330
No reviewers
Labels
No Label
area/internal-code
changes requested
confirmed
dependencies
duplicate
good first issue
help wanted
hosting
invalid
kind/bug
kind/feature
question
wontfix
No Milestone
No project
No Assignees
3 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: vikunja/frontend#2330
Loading…
Reference in New Issue
No description provided.
Delete Branch "feature/enable-related-task-done"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Related forum thread: https://community.vikunja.io/t/task-checklists/680/11?u=kolaente
There is one caveat remaining: If the user does not have the right to mark the related task as done an error message will be shown and the task won't be marked as done. Currently the api does not provide a way for us to check this in advance (without loading each task individually) so we can't really prevent this.
Hi konrad!
Thank you for creating a PR!
I've deployed the changes of this PR on a preview environment under this URL: https://2330-feature-enable-related-task-done--vikunja-frontend-preview.netlify.app
You can use this url to view the changes live and test them out.
You will need to manually connect this to an api running somehwere. The easiest to use is https://try.vikunja.io/.
Have a nice day!
feat: allow marking a related task done directly from the listto feat: allow marking a related task done directly from the list of related tasksI would love if we could fix the related task script setup and apply this to that pull request.
@ -317,0 +324,4 @@
async toggleTaskDone(task: ITask) {
if (task.done) {
playPop()
Unsure: Wouldn't it make sense to play this from the store when we update the task an the
done
prop has changed?Yes.
Done.
@ -389,1 +415,4 @@
.task-done-checkbox {
padding: 0;
height: 18px; // The exact height of the checkbox in the container
Why do we need to set a height from outside here?
Because otherwise the height of the actual checkbox in the
<Fancycheckbox
component is too much resulting in a weired positioning of the checkbox. Setting the height here is a workaround until we fix the styling of the component. I didn't want to do this in this PR because the component is used in a lot of places and the change has potential to break a few things. Better do it in another PR.Okay. Can you prefix it with a
// FIXME:
or// HACK:
then?Done.
Ohh right we also have that open! I think we should merge the other one first.
1ffcd5ff2f
tof24ac01e36
#2330 (comment)
I ported this over to #1939 in
08dc289260
So we'll close this one in favour of #1939?