🐛 Removing a sub question answer should change submit availability
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Summary
Selecting "Stimulus Case Study," select sub question Multiple Choice as an example. Enter text and answers. select one as correct. click remove of the correct answer. This happens when the user select Multi Choice as the main question type as well. This probably also happens for SATA.
The user should not be able to submit the form. They can submit it without any answers.
Acceptance Criteria
- Answers must be present for the submit button to be enabled
Screenshots or Video
Testing Instructions
To be filled out by dev
Notes
Contributor guide
No contributing guide indexed for this repository
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 reproducing the described Stimulus Case Study flow with a Multiple Choice sub-question, then remove the selected correct answer and inspect the form's submit availability and answer-removal handling. Done means the submit button stays disabled whenever no answers are present, including for main Multiple Choice and SATA questions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100