Updated "Task" properties and Schema#206
Conversation
… per function (under the Task based calls).
|
Hi @kolaente @paulhybryant @MikeyC3040 , Checking if youd like more on this PR or have a process in mind for adds like this? Thanks! |
|
Hey sorry for the late reply, seems like I totally forgot to reply here. Happy to merge this, but please fix the indention first. |
Hoping that last commit cleans that up. If needed I can prune and reapply to clean it up a bit further. Just let me know! Thanks @kolaente ! |
kolaente
left a comment
kolaente
left a comment
There was a problem hiding this comment.
There seem to be many properties related to task position, not all of these are useful. I think we can do with the task position entity (the one that calls the position endpoint).
jax0m
left a comment
jax0m
left a comment
There was a problem hiding this comment.
I did update this to remove the duplicate properties (looked like I copy and pasted that 3x lol).
However, likely going to add another commit today that will flesh out a bit of what I was looking to add originally (reminders).
… go but this better includes the enum from the reminder picker relative to the period
| request: { | ||
| method: 'DELETE', | ||
| url: '=/tasks/{{$parameter.taskId}}/labels/{{$parameter.taskLabel}}', | ||
| // FIX: Updated to use labelID instead of non-existent taskLabel |
There was a problem hiding this comment.
Yeah ive got to go through this with a finer tooth comb for sure, also trying to work out an idea for the reminders that would work with relative to and absolute time reminders.
Part of the plan for today, and appreciate the look you've been able to give so far!
|
Converted back to draft while work in progress! |
…ly fields - Remove read-only fields from options collection: - created, createdBy, updated, taskIndex - Change dateTime fields to string type with ISO 8601 format: - dueDateTime, endDateTime, startDateTime - Updated descriptions to require timezone (e.g., 2026-03-18T17:40:31-07:00) - Remove Reminder collection (shelved for future work): - relativePeriod, relativeTo, reminder - Add Additional Query Parameters collection for getAll operation: - expand (multiOptions: subtasks, buckets, reactions, comments) - filter (string) - filterIncludeNulls (boolean, default: false) - perPage (number) - page (number) - search (string) - sortBy (17 options, default: id) - orderBy (asc/desc, default: asc) - Fix typo in relationKind options: - "Coped To" → "Copied To" - "Blocked" → "Blocked By" for consistency
|
Swapped out a couple more things after some test driving of the module overall. Happier with it overall minus the reminders at the moment since that one is/was a little trickier. Would love to see what you all think about it so far if you get a chance. |
2 participants
Hi, I found when I was trying to implement some functions via n8n I was unable to call to find some items related to "reminders" on the task based aspects of the node that are documented in the API.
After taking a look at the module I noticed that several of the items related to tasks were missing properties that are present on the current/later versions of Vikunja.
This is my attempt to implement those or understand the process that you would like to have PRs submitted/tested/etc!