Skip to content

[Bugfix:RainbowGrades] Save Gradeables Configurations#12126

Merged
bmcutler merged 18 commits intomainfrom
gradeables-settings-nonsticky-fix
Nov 12, 2025
Merged

[Bugfix:RainbowGrades] Save Gradeables Configurations#12126
bmcutler merged 18 commits intomainfrom
gradeables-settings-nonsticky-fix

Conversation

@RyanStyron
Copy link
Copy Markdown
Contributor

Why is this Change Important & Necessary?

There are currently three toggles in the Category/Gradeable Configuration section of the Grades Configuration page: Extra credit, Remove lowest, and Per Gradeable Percents (displayed below). These toggles do not currently save after being changed; most problematic is that per gradeable percentages are not retrieved properly. Further, there is a lack of intuition with respect to certain toggles in that, for instance, an instructor can assign a "remove lowest" value, and then disable the "remove lowest" toggle, but the value would retain its pre-disabled value and applied as such rather than being assigned to zero. This applies to per gradeable percentages as well. As opposed to "per gradeables percent" having both a global and local toggle (with respect to a given course's settings), it seems more logical to have them isolated purely as gradeable-specific. Similarly, disabling a per gradeable percentage should be disabled (coupled with an attached error message) unless all gradeables have equal weightings; same logic for remove lowest toggling.

What is the New Behavior?

Initial view:
image
image
image

Update view:
image
image
image
image

What steps should a reviewer take to reproduce or test the bug or new feature?

As an instructor, navigate to Grades Configuration of a course and apply various toggles and values to respective configurations.

Automated Testing & Documentation

Other information

@codecov
Copy link
Copy Markdown

codecov bot commented Oct 3, 2025

Codecov Report

❌ Patch coverage is 52.94118% with 8 lines in your changes missing coverage. Please review.
✅ Project coverage is 21.74%. Comparing base (fef0849) to head (f14f9a7).
⚠️ Report is 20 commits behind head on main.

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff            @@
##               main   #12126   +/-   ##
=========================================
  Coverage     21.73%   21.74%           
- Complexity     9598     9605    +7     
=========================================
  Files           268      268           
  Lines         36006    36019   +13     
  Branches        475      475           
=========================================
+ Hits           7827     7832    +5     
- Misses        27708    27716    +8     
  Partials        471      471           
Flag Coverage Δ
autograder 21.39% <ø> (ø)
js 2.07% <ø> (ø)
migrator 100.00% <ø> (ø)
php 20.74% <52.94%> (+<0.01%) ⬆️
python_submitty_utils 80.08% <ø> (ø)
submitty_daemon_jobs 90.72% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@RyanStyron RyanStyron changed the title [Bugfix:Gradeables] Save Gradeables Configurations [Bugfix:RainbowGrades] Save Gradeables Configurations Oct 3, 2025
Copy link
Copy Markdown
Contributor

@Rkoester47 Rkoester47 left a comment

Choose a reason for hiding this comment

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

I tested the changes here in the Rainbow Grades Configuration, and was able to reproduce all of the features listed in the PR. The category/ gradeable section does have two toggle buttons now.

Also, I was able to test both attempting to remove "drop lowest" while a number of lowest drops were specified, as well as removing "per gradeable percents" while having at least one grade be worth a different amount than the others. In both cases, the warning did pop up to let me know that I could not make those changes to the configuration.

Overall, the changes to the site match the PR and have improved the functionality of the gradeable configuration tools. The new functionality is more intuitive and in-line with what someone configuring a gradeable should expect.

@github-project-automation github-project-automation bot moved this from Seeking Reviewer to Awaiting Maintainer Review in Submitty Development Oct 3, 2025
Copy link
Copy Markdown
Contributor

@lavalleeale lavalleeale left a comment

Choose a reason for hiding this comment

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

I tested locally and can confirm the bugs listed in the PR description are fixed and for someone not familiar with configuring rainbow grades it makes a lot more sense to me now

@RyanStyron
Copy link
Copy Markdown
Contributor Author

Added a toggle for the configuration settings via the pencil icon. By default, the configuration settings, including individual per gradeable percents and bucket-level "remove lowest" values, are hidden, but when the pencil is clicked, the configurations become visible.

@automateprojectmangement automateprojectmangement bot moved this from Awaiting Maintainer Review to In Review in Submitty Development Oct 9, 2025
Copy link
Copy Markdown
Contributor

@Rkoester47 Rkoester47 left a comment

Choose a reason for hiding this comment

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

All of the updates and UI changes since my initial approval look clean and help improve site readability and usability.

@github-project-automation github-project-automation bot moved this from In Review to Awaiting Maintainer Review in Submitty Development Oct 10, 2025
Copy link
Copy Markdown
Contributor

@lavalleeale lavalleeale left a comment

Choose a reason for hiding this comment

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

This definitely works as intended, but as a new rainbow grades user, having to click the pencil to view the settings make it very hard for a new user to know that more settings are there

@automateprojectmangement automateprojectmangement bot moved this from Awaiting Maintainer Review to In Review in Submitty Development Oct 14, 2025
Copy link
Copy Markdown
Contributor

@lavalleeale lavalleeale left a comment

Choose a reason for hiding this comment

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

The code and the experience are both very good now, the bugs are fixed and the UI is a lot easier to understand

@github-project-automation github-project-automation bot moved this from In Review to Awaiting Maintainer Review in Submitty Development Oct 21, 2025
@RyanStyron RyanStyron moved this from Awaiting Maintainer Review to Ready to Merge in Submitty Development Nov 11, 2025
@bmcutler bmcutler merged commit cf4f84e into main Nov 12, 2025
25 checks passed
@bmcutler bmcutler deleted the gradeables-settings-nonsticky-fix branch November 12, 2025 22:50
@github-project-automation github-project-automation bot moved this from Ready to Merge to Done in Submitty Development Nov 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

4 participants