-
Notifications
You must be signed in to change notification settings - Fork 22
fix: quiz submission before prerequisites #135
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Current Behavior: - Users could submit quizzes without prerequisites being completed. - Backend would reject submissions after answers were already filled, causing frustration. Fix: - Added client-side prerequisite check before allowing quiz submission. - Users are now prompted to complete missing prerequisites before submitting answers. - Ensures a smoother user experience and prevents unnecessary time waste. Signed-off-by: Sunny <[email protected]>
3377f1d to
c5190b3
Compare
|
This PR addresses the quiz submission issue and fixes the submission flow. Could you please review it when you get a chance and merge if it looks good? Thanks! |
|
Hi @saurabhraghuvanshii , This PR ( Thanks in advance! |
|
@bashSunny101 please be patient and wait we can't merge pr directly. |
layouts/test/single.html
Outdated
|
|
||
| // Check for existing submission | ||
| const existingGradeResult = window.academyContext?.progressTracker?.progress?.grades[testId] || null; | ||
|
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
seems unnecessary
RanitMukherjee
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good work 🚀 , LGTM as far as the code is concerned!
|
Kindly let me know if any changes are to be made😊 |
|
Hi, |
|
@bashSunny101 please message on slack for it. I don't have access. |
Signed-off-by: Sunny Pal <[email protected]>
|
@bashSunny101 the issue has already been fixed in a separate pr and released . We can close this pr . Don't feel disheartened there are more issues than we can count .. |
|
Thanks for the update. I just wanted to clarify — I had opened this PR earlier and have been actively following up with comments and feedback. I didn’t notice any other PR addressing the same issue before mine. Could you please confirm which PR fixed it? It’ll help me understand the changes better and avoid overlaps in the future. Either way, I really appreciate the feedback and will definitely look for more issues to contribute to! 😊 |
Current Behavior:
Fix:
Notes for Reviewers
This PR fixes #122
Signed commits