Mandatory state of a Selection Yes/No column
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 214
- Forks
- 52
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 82
Description
Is your feature request related to a problem? Please describe.
Sometimes it is desirable or could be helpful to have a Selection Yes/No Column mandatory to be changed in a view, for example to flag a row as already processed or flag a client as registered.
Right now, even if a Selection Yes/No Column is set as mandatory the default state is accepted as, of course, a default Yes or No is already a perfectly fine value in itself. Nevertheless this preventes having this kind of columns as mandatory at all.
Describe the solution you'd like
If a Selection Yes/No Column is set as mandatory in a view, only the non-default state should be accepted to be able to save this row.
Describe alternatives you've considered
No response
Additional context
No response
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
No file or test is named. Start by locating the Selection Yes/No column's mandatory validation and the row-save flow in the JavaScript app. Check how default and non-default states are represented, then verify that mandatory columns reject the default state and accept the changed state.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100