Skip to content

Conversation

@lizzie-liu
Copy link
Contributor

@lizzie-liu lizzie-liu commented Nov 17, 2025

Proposed Changes

Migrating the Course Summary Table to use @tanstack/react-table v8.

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)
🎨 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) X

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
Copy link
Collaborator

coveralls commented Nov 18, 2025

Pull Request Test Coverage Report for Build 19452209077

Details

  • 22 of 28 (78.57%) changed or added relevant lines in 1 file are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+0.03%) to 91.69%

Changes Missing Coverage Covered Lines Changed/Added Lines %
app/javascript/Components/course_summaries_table.jsx 22 28 78.57%
Totals Coverage Status
Change from base Build 19439765710: 0.03%
Covered Lines: 43307
Relevant Lines: 46463

💛 - Coveralls

const columnHelper = this.columnHelper;
return [
columnHelper.accessor("hidden", {
id: "hidden",
Copy link
Collaborator

Choose a reason for hiding this comment

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

This column is actually still appearing in the table (see screenshot below). I think this actually might be a problem with other v8 tables as well, I recall seeing it somewhere else. Please modify this code so that the column is fully hidden. You may need to change the underlying Table component implementation we've defined.

columnHelper.accessor("hidden", {
id: "hidden",
filterFn: (row, columnId, filterValue) => {
if (filterValue) return true; // If filterValue true, show all rows
Copy link
Collaborator

Choose a reason for hiding this comment

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

This code should be simplified; follow the same structure as the original implementation. You can leave a comment explaining what conditions are checked.


updateShowHidden = event => {
let showHidden = event.target.checked;
let filtered = [];
Copy link
Collaborator

Choose a reason for hiding this comment

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

You should not change this code other than the renaming of the state

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants