Conversation
Adds the plan and entitlements fields returned by the team presenter (outline/outline#13896) to the Team schema, along with the Plan and PlanFeature enums. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HM4jCsoieq7u153jPBjx7e
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
2 participants
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
Documents two new fields returned by the team presenter, introduced upstream in outline/outline#13896 ("feat: Add plan-based feature entitlements"):
plan— the subscription plan the workspace is on (community,standard,business,enterprise,legacy).entitlements— an array of plan-based features the workspace is entitled to use.Both are added unconditionally to the team presenter output, so they appear on the
Teamobject wherever it is returned (e.g.auth.info).Changes
planandentitlementsproperties to theTeamschema.PlanandPlanFeaturecomponent enum schemas to back those fields, matching the enum values in the upstreamPlan/PlanFeaturedefinitions.spec3.jsonwas regenerated automatically by the pre-commit hook.Other PRs merged in the same window (table-control fixes, comments-API perf refactor, group-sync fix, template lazy-loading, Prosemirror memoization, users-table UI) do not change the public API input schema or output shape.
🤖 Generated with Claude Code
https://claude.ai/code/session_01HM4jCsoieq7u153jPBjx7e
Generated by Claude Code