Add 200-outcome limit guidance to discrete question error messages and guidelines#4413
Add 200-outcome limit guidance to discrete question error messages and guidelines#4413SylvainChevalier wants to merge 2 commits intomainfrom
Conversation
…d guidelines Update the step validation error message across all locales (en, es, cs, zh, zh-TW, pt) to inform users that questions with more than 200 possible outcomes should use the continuous question type. Also add this guidance to the question writing guidelines page. Closes #4410 Co-authored-by: Sylvain <SylvainChevalier@users.noreply.github.com>
|
@claude also change the check for number of bins during discrete question creation. |
|
Claude finished @SylvainChevalier's task in 6m 25s —— View job Added backend validation check for discrete question bin limit
Added server-side validation in View commit · · |
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Tip Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Enforce the 200-outcome limit server-side in QuestionWriteSerializer.validate() to prevent bypassing the frontend validation via direct API calls. Co-authored-by: Sylvain <SylvainChevalier@users.noreply.github.com>
Cleanup: Preview Environment RemovedThe preview environment for this PR has been destroyed.
Cleanup triggered by PR close at 2026-02-25T13:50:57Z |
Closes #4410
Summary
Test plan
Generated with Claude Code