Add UI schema to task discovery response to help frontend build forms
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
Start by examining how the task discovery endpoint is represented in this repository and how task parameters are currently described with JSON Schema. Define what the combined JSON Schema and UI schema response should contain, then verify that it supports frontend form generation and task validation.
Written by the indexing model from the issue text.
Description
Feature request
Description
Regarding this issue about validating tasks https://github.com/open-rmf/rmf-web/issues/684. Afaik, there are several blockers for us to resolve it.
- The rmf task discovery endpoint is not implemented yet
- The task discovery uses json schema to describe the params of a task
- Problem is that json schema is very powerful/flexible, I have tried building a form from json schema before but there are too many features which makes the whole process super complicated.
- There are some similar OSS projects like https://jsonforms.io/ and https://github.com/rjsf-team/react-jsonschema-form, but they require a ui schema to be written beforehand so it won't quite work for our case. Given that this is the approach they use, my conclusion is that going from json schema -> ui forms directly is actually a very complex challenge.
My proposal is to have task discovery contain both the json schema and a ui schema, with this, we can build forms for any tasks and validate them.
- Dominant language
- Rust
- Stars
- 2
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from open-rmf/rmf_api_msgs
-
Write the `status` / `issues` / `commission` boundary into `robot_state.json` descriptionsMay be free again @mxgrey claimed this 81 days ago, and no pull request is open. Open
open-rmf/rmf_api_msgs#65 · 1 assignee ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
open-rmf/rmf_api_msgs#52 · 2 comments ·
-
Update CI to also build downstream projectsMay be free again @Yadunund claimed this 1269 days ago, and no pull request is open. Openenhancement
open-rmf/rmf_api_msgs#37 · 1 assignee ·
-
Create some tests and CI workflowMay be free again @koonpeng claimed this 1526 days ago, and no pull request is open. Openenhancement
open-rmf/rmf_api_msgs#29 · 2 assignees ·
-
Schema for recurring tasksMay be free again A pull request for this issue was closed without being merged. Openenhancement
Difficulty 5/5 Over a week Newbie friendliness 20/100
open-rmf/rmf_api_msgs#16 ·
All issues in open-rmf/rmf_api_msgs
Similar issues
-
[Bug]: opencode_go chat route drops reasoning_effort (even 'none'), while the same endpoint honors it via custom_llm_provider=openaiPossibly taken @arvindkumar-ship-it claimed this today. Openllm translation
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
BerriAI/litellm#51871 · 1 comment ·
Maintainers usually reply within 1 day
-
comp-formats
Difficulty 2/5 Half a day Newbie friendliness 64/100
ClickHouse/ClickHouse#131694 ·
Maintainers usually reply within 1 day
-
cli: `execCargoMetadata` decodes stdout per chunk, corrupting non-ASCII paths across pipe boundariesOpen
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
C-Bug S-Needs-Triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
bevyengine/bevy#26558 ·
Maintainers usually reply within 2 days