#7674: Ordering Sections on the Section-Specific Settings Table for Timed Assessments

[lizzie-liu]

Proposed Changes

Fixed the timed assessment section-specific settings table to be alphanumerically ordered by section name.
Closes #7674

Screenshots of your changes (if applicable)

Associated documentation repository pull request (if applicable)

Type of Change

(Write an X or a brief description next to the type or types that best describe your changes.)

Type	Applies?
🚨 Breaking change (fix or feature that would cause existing functionality to change)
✨ New feature (non-breaking change that adds functionality)
🐛 Bug fix (non-breaking change that fixes an issue)	X
🎨 User interface change (change to user interface; provide screenshots)
♻️ Refactoring (internal change to codebase, without changing functionality)
🚦 Test update (change that only adds or modifies tests)
📦 Dependency update (change that updates a dependency)
🔧 Internal (change that only affects developers or continuous integration)

Checklist

(Complete each of the following items for your pull request. Indicate that you have completed an item by changing the [ ] into a [x] in the raw text, or by clicking on the checkbox in the rendered description on GitHub.)

Before opening your pull request:

• I have performed a self-review of my changes.
  • Check that all changed files included in this pull request are intentional changes.
  • Check that all changes are relevant to the purpose of this pull request, as described above.
• I have added tests for my changes, if applicable.
  • This is required for all bug fixes and new features.
• I have updated the project documentation, if applicable.
  • This is required for new features.
• If this is my first contribution, I have added myself to the list of contributors.

After opening your pull request:

• I have updated the project Changelog (this is required for all changes).
• I have verified that the pre-commit.ci checks have passed.
• I have verified that the CI tests have passed.
• I have reviewed the test coverage changes reported by Coveralls.
• I have requested a review from a project maintainer.

Questions and Comments

(Include any questions or comments you have regarding your changes.)

[coveralls]

Pull Request Test Coverage Report for Build 18331556380

Details

• 0 of 1 (0.0%) changed or added relevant line in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 91.87%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
app/controllers/assignments_controller.rb	0	1	0.0%

Totals
Change from base Build 18331268749:	0.0%
Covered Lines:	42356
Relevant Lines:	45381

---

💛 - Coveralls

[david-yz-liu]

The number is incorrect: it should refer to the pull request number (7690), not the issue number.

Also please mention that this change is on the assignment settings form.

[david-yz-liu]

I've updated the Rubocop configuration for pre-commit, though to be honest I'm not sure why you ran into this issue. In any case, please do a pull from upstream master and then revert these changes. They should no longer be flagged by Rubocop.

[david-yz-liu]

Nice work, @lizzie-liu!