Skip to content

Update user info during roster sync#7865

Open
donny-wong wants to merge 4 commits intoMarkUsProject:masterfrom
donny-wong:update_user_info_roster_sync
Open

Update user info during roster sync#7865
donny-wong wants to merge 4 commits intoMarkUsProject:masterfrom
donny-wong:update_user_info_roster_sync

Conversation

@donny-wong
Copy link
Contributor

@donny-wong donny-wong commented Mar 13, 2026

Proposed Changes

(Describe your changes here. Also describe the motivation for your changes: what problem do they solve, or how do they improve the application or codebase? If this pull request fixes an open issue, use a keyword to link this pull request to the issue.)

Currently when doing Roster Sync with Canvas, user information gets inputed during creation only. We want to also do this during the update process. Specifically for the following user information:

  • first_name
  • last_name
  • display_name
  • email
  • id_number
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) x
🐛 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)

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 Mar 13, 2026

Pull Request Test Coverage Report for Build 23153403458

Details

  • 40 of 43 (93.02%) changed or added relevant lines in 2 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+0.001%) to 91.676%

Changes Missing Coverage Covered Lines Changed/Added Lines %
app/helpers/lti_helper.rb 7 10 70.0%
Totals Coverage Status
Change from base Build 23091690132: 0.001%
Covered Lines: 45116
Relevant Lines: 48399

💛 - Coveralls

@donny-wong donny-wong force-pushed the update_user_info_roster_sync branch from 676c6fe to 4e8e5ab Compare March 16, 2026 16:06
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.

Doing Roster Sync with Canvas, it should still update user information on MarkUs side

3 participants