Speak of the LMS generically, not Canvas specifically
The tool targets any LTI 1.3 platform; Canvas is the primary target but nothing outside the Canvas-specific custom variable substitutions depends on it. User-facing strings and the README now say "LMS" except where a mechanism genuinely is Canvas's (the $Canvas.* / com.instructure.* substitutions and their handling), and the README states plainly that the tool has so far been exercised only against the saltire emulator, not yet a production LMS. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
@@ -113,7 +113,7 @@ class Student(Base):
|
||||
__tablename__ = "students"
|
||||
|
||||
id: Mapped[int] = mapped_column(primary_key=True)
|
||||
# The LTI "sub" claim: stable, opaque, unique per Canvas user.
|
||||
# The LTI "sub" claim: stable, opaque, unique per LMS user.
|
||||
canvas_user_id: Mapped[str] = mapped_column(String(255), unique=True)
|
||||
name: Mapped[str | None] = mapped_column(String(255))
|
||||
sortable_name: Mapped[str | None] = mapped_column(String(255))
|
||||
|
||||
Reference in New Issue
Block a user