Setting Due Date on Add Task in RTM API
Hello,
I've composed an Alexa skill that enables adding tasks via RTM's API. It's working fine, but I've discovered that the API's rtm.tasks.add method ignores the parameter, e.g.
{
due: '2025-01-01'
}
And as a result tasks were being added without any due date (which, in my utilzation of RTM, makes the tasks effectively hidden from view).
As a workaround, I'm setting the tasks to be parsed using natural language to set a due date:
{
parse: 1,
name: task + ' today'
}
Because the yet-to-be-created tasks don't have a , I don't see a way to use the rtm.tasks.setDueDate method.
Questions:
1. Is there a way to use setDueDate() "on the fly" so to speak during task creation?
2. What would be my next steps to suggest a modification to the V2 API to parse ISO date strings as arguments on a parameter for the rtm.tasks.add method?
I've composed an Alexa skill that enables adding tasks via RTM's API. It's working fine, but I've discovered that the API's rtm.tasks.add method ignores the parameter, e.g.
{
due: '2025-01-01'
}
And as a result tasks were being added without any due date (which, in my utilzation of RTM, makes the tasks effectively hidden from view).
As a workaround, I'm setting the tasks to be parsed using natural language to set a due date:
{
parse: 1,
name: task + ' today'
}
Because the yet-to-be-created tasks don't have a , I don't see a way to use the rtm.tasks.setDueDate method.
Questions:
1. Is there a way to use setDueDate() "on the fly" so to speak during task creation?
2. What would be my next steps to suggest a modification to the V2 API to parse ISO date strings as arguments on a parameter for the rtm.tasks.add method?
Hmm... I think the forum post filtered anything I put inside brackets (sorry). Let me try again:
I've composed an Alexa skill that enables adding tasks via RTM's API. It's working fine, but I've discovered that the API's rtm.tasks.add method ignores the "due" parameter, e.g.
{
due: '2025-01-01'
}
And as a result tasks were being added without any due date (which, in my utilzation of RTM, makes the tasks effectively hidden from view).
As a workaround, I'm setting the tasks to be parsed using natural language to set a due date:
{
parse: 1,
name: task + ' today'
}
Because the yet-to-be-created tasks don't have a "task_id" I don't see a way to use the rtm.tasks.setDueDate method.
Questions:
1. Is there a way to use setDueDate() "on the fly" so to speak during task creation?
2. What would be my next steps to suggest a modification to the V2 API to parse ISO date strings as arguments on a parameter for the rtm.tasks.add method?
I've composed an Alexa skill that enables adding tasks via RTM's API. It's working fine, but I've discovered that the API's rtm.tasks.add method ignores the "due" parameter, e.g.
{
due: '2025-01-01'
}
And as a result tasks were being added without any due date (which, in my utilzation of RTM, makes the tasks effectively hidden from view).
As a workaround, I'm setting the tasks to be parsed using natural language to set a due date:
{
parse: 1,
name: task + ' today'
}
Because the yet-to-be-created tasks don't have a "task_id" I don't see a way to use the rtm.tasks.setDueDate method.
Questions:
1. Is there a way to use setDueDate() "on the fly" so to speak during task creation?
2. What would be my next steps to suggest a modification to the V2 API to parse ISO date strings as arguments on a parameter for the rtm.tasks.add method?
Log in
to post a reply.