Skip to content

Score screen indicates max score in LTI contexts - #1686

Merged
clpetersonucf merged 1 commit into
ucfopen:dev/11.0.1from
clpetersonucf:issue/1674-score-screen-should-indicate-max-score
Apr 15, 2026
Merged

Score screen indicates max score in LTI contexts#1686
clpetersonucf merged 1 commit into
ucfopen:dev/11.0.1from
clpetersonucf:issue/1674-score-screen-should-indicate-max-score

Conversation

@clpetersonucf

@clpetersonucf clpetersonucf commented Mar 24, 2026

Copy link
Copy Markdown
Member

Resolves #1674

  • Adds score_submitted to LtiPlayState model, with null=True to allow null values for previously stored play states.
  • The lti section of the score details endpoint now includes the score_submitted value as max_score.
  • Adjusted score screen components to check for a max_score value and if different from the previous score, the LTI overview section indicates the max score value submitted for the given play:
Screenshot 2026-03-24 at 5 00 33 PM

@FrenjaminBanklin FrenjaminBanklin left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Everything looks sane enough.

Rubber stamping so we can get this running in a more easily testable environment.

@clpetersonucf
clpetersonucf merged commit 46c444c into ucfopen:dev/11.0.1 Apr 15, 2026
2 checks passed
@clpetersonucf
clpetersonucf deleted the issue/1674-score-screen-should-indicate-max-score branch April 15, 2026 12:56
@clpetersonucf clpetersonucf mentioned this pull request Apr 29, 2026
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.

2 participants