Skip to content
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

Limit max questions per section to 25. #12487

Merged
merged 3 commits into from
Jul 29, 2024

Conversation

rtibbles
Copy link
Member

@rtibbles rtibbles commented Jul 25, 2024

Summary

  • Limits max questions per section to 25
  • Hides add more questions button in section editor when section already has the max number of questions

Reviewer guidance

Does this make the learner and coach experience better?


Testing checklist

  • Contributor has fully tested the PR manually
  • If there are any front-end changes, before/after screenshots are included
  • Critical user journeys are covered by Gherkin stories
  • Critical and brittle code paths are covered by unit tests

PR process

  • PR has the correct target branch and milestone
  • PR has 'needs review' or 'work-in-progress' label
  • If PR is ready for review, a reviewer has been added. (Don't use 'Assignees')
  • If this is an important user-facing change, PR or related issue has a 'changelog' label
  • If this includes an internal dependency change, a link to the diff is provided

Reviewer checklist

  • Automated test coverage is satisfactory
  • PR is fully functional
  • PR has been tested for accessibility regressions
  • External dependency files were updated if necessary (yarn and pip)
  • Documentation is updated
  • Contributor is in AUTHORS.md

@rtibbles rtibbles requested a review from radinamatic July 25, 2024 15:49
@github-actions github-actions bot added DEV: backend Python, databases, networking, filesystem... DEV: frontend labels Jul 25, 2024
@radinamatic
Copy link
Member

I like the fact that the limit is fixed in the input field, I'm just missing explicit message to the user.

Especially if they already added 20 questions and they click the button Add more questions in the Settings sidebar. We should at least conditionally remove that button if the section already has 20 questions, and optionally (if possible and not too hacky) already include the option to add another section (not sure if that is doable from the settings sidebar of another section).

2024-07-25_19-44-52

There is already a max question string, you would only need to set the variable to be fixed to 20.

@rtibbles
Copy link
Member Author

Ah yes, well, that would need to be fixed regardless of the limit, if it's not disabling for 20, it won't be disabling for 50.

@github-actions github-actions bot added the APP: Coach Re: Coach App (lessons, quizzes, groups, reports, etc.) label Jul 26, 2024
@rtibbles rtibbles marked this pull request as ready for review July 26, 2024 18:29
@rtibbles rtibbles changed the title Limit max questions per section to 20. Limit max questions per section to 25. Jul 26, 2024
@radinamatic
Copy link
Member

Great, the button is now not active when more than 25 questions are specified in the input field! 👍🏽

2024-07-28_03-00-27

Copy link
Member

@radinamatic radinamatic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! 💯 :shipit:

Copy link
Member

@marcellamaki marcellamaki left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

code review looks fine, and going through the UI, agree with Radina that this looks good. And I think it's a preferable workflow

@marcellamaki marcellamaki merged commit 7f833b4 into learningequality:release-v0.17.x Jul 29, 2024
33 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
APP: Coach Re: Coach App (lessons, quizzes, groups, reports, etc.) DEV: backend Python, databases, networking, filesystem... DEV: frontend
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants