Schema for recurring tasks

Open
  • Is something wrong?
#16 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

  • #25 by @luca-della-vedova — closed without merging

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Domain
api

Research direction

Review the recurring-task schema discussion in this issue and the linked rmf_ros2 issue 103 first. Resolve the proposed CRUD schemas and periodicity representation, including the cron-like fields and start/end dates; completion criteria are not yet defined in the issue.

Written by the indexing model from the issue text.

Description

enhancement

Starting a discussion on the schemas for recurring tasks which is needed for https://github.com/open-rmf/rmf_ros2/issues/103

We can have four types of schemas for standard CRUD operations. Common across these will be a sub-schema for describing the periodicity of the tasks and @aarushg22 suggested mimicking the cron datetime format for this.

{
  "seconds" : "0",
  "minutes" : "0",
  "hours" : "15",
  "day_of_week" : "1",
  "month" : "0",
  "day_of_month" : "*",
  "start_date" : "2022-01-01", 
  "end_date" : "2022-01-31"
}
Dominant language
Rust
Stars
2
Forks
11
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from open-rmf/rmf_api_msgs

All issues in open-rmf/rmf_api_msgs

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.