Document invitedBy field on User schema - #44
Open
tommoor wants to merge 1 commit into
Open
Conversation
Adds the invitedBy property, populated only for admin viewers, mirroring the users.list change from outline/outline#13325.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a new
invitedByproperty to theUserschema, mirroring the field added to theusers.listresponse in outline/outline#13325. The field is a nestedUserobject identifying who invited the user, and is only populated in responses to admin viewers.Recent PRs Reviewed
Reviewed all pull requests merged in outline/outline over the last day (2026-08-07 → 2026-08-08). Most were internal fixes with no public API impact:
data) — bug fix only, existing schema already documentsdataas non-nullableauth.infocollaborationToken) — field was never documented in the spec (only issued to APP-type sessions)suggestions.mentionguest scoping) — endpoint not documented in the specinvitedBytousers.listresponse → documented in this PRTest plan
yarn validatepassesspec3.jsonregenerated via pre-commit hookGenerated by Claude Code