GUI: Clear handling of optional parameters
Open
Nobody has claimed this yet.
essreduce
- Dominant language
- Python
- Stars
- 1
- Forks
- 3
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 17
Description
We should clearly indicate which parameters are optional.
See also https://github.com/scipp/ess/issues/501#issue-2717068449:
- Which entries are compulsory or optional?
Contributor 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.
Research direction
Start by reviewing the GUI parameter-entry flow and the related discussion in scipp/ess#501, which asks which entries are compulsory or optional. Identify where parameter labels or controls are defined, then confirm that optional parameters are visibly distinguished from compulsory ones throughout the GUI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100