Use sort keys / groups to better present options when using rose edit
- Dominant language
- Python
- Stars
- 5
- Forks
- 3
- Avg merge
- 5d 6h
- Merged PRs (30d)
- 8
Description
The `ROOTPATH_*` and `DRS_*` options from the `rose_suite.conf` file should be at the bottom of the `rose edit` view / in a separate group, along with `TEST`. The remaining options (`SITE`, `MODULE_NAME` and `MAX_PARALLEL_TASKS`) should be at the top, in this order.
The model run specification should be in a separate group from this, and if possible in a separate panel. The GC ancil workflow would be a good example of how to put variables into sections / panels.
**Details**
- Estimate: 1 day
Contributor guide
Research direction
Start in the rose edit configuration for rose_suite.conf and inspect the GC ancil workflow as the issue suggests, focusing on how variables are assigned to sections or panels. Confirm where ROOTPATH_*, DRS_*, TEST, SITE, MODULE_NAME, MAX_PARALLEL_TASKS, and the model run specification are defined. Done means the options appear in the requested order and groups, with a separate panel if supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100