Skip to content

Add 23 scheduleEntityTheme color members (v1.0 + beta)#9874

Closed
raulfernandes wants to merge 1 commit intomicrosoftgraph:mainfrom
raulfernandes:shifts-additional-schedule-entity-themes
Closed

Add 23 scheduleEntityTheme color members (v1.0 + beta)#9874
raulfernandes wants to merge 1 commit intomicrosoftgraph:mainfrom
raulfernandes:shifts-additional-schedule-entity-themes

Conversation

@raulfernandes
Copy link
Copy Markdown
Contributor

Summary

  • Extends the scheduleEntityTheme enum in api-reference/v1.0/resources/enums.md and api-reference/beta/resources/enums.md with 23 new color themes, added after unknownFutureValue per evolvable-enum convention.
  • New members (values 13–35 in CSDL): darkRed, cranberry, darkOrange, bronze, peach, gold, lime, forest, lightGreen, jade, lightTeal, darkTeal, steel, skyBlue, blueGray, lavender, lilac, plum, magenta, darkBrown, beige, charcoal, silver.
  • Sourced from the Shifts schema PR: https://msazure.visualstudio.com/One/_git/AD-AggregatorService-Workloads/pullrequest/15488646

Test plan

  • Doc build / link-check passes in CI
  • Spot-check rendered enum table on resources/enums.md (v1.0 and beta)

🤖 Generated with Claude Code

Aligns the enum table in api-reference/{v1.0,beta}/resources/enums.md with
the Shifts schema change that extends scheduleEntityTheme with additional
color themes (darkRed, cranberry, darkOrange, bronze, peach, gold, lime,
forest, lightGreen, jade, lightTeal, darkTeal, steel, skyBlue, blueGray,
lavender, lilac, plum, magenta, darkBrown, beige, charcoal, silver).

Schema PR: https://msazure.visualstudio.com/One/_git/AD-AggregatorService-Workloads/pullrequest/15488646

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@learn-build-service-prod
Copy link
Copy Markdown
Contributor

Learn Build status updates of commit 7e93c82:

✅ Validation status: passed

File Status Preview URL Details
api-reference/beta/resources/enums.md ✅Succeeded
api-reference/v1.0/resources/enums.md ✅Succeeded

For more details, please refer to the build report.

@raulfernandes
Copy link
Copy Markdown
Contributor Author

Closing — this change needs to land in the private microsoftgraph/microsoft-graph-docs repo per internal contribution guidelines (branch-based collaboration, not personal fork). Continuing in microsoftgraph/microsoft-graph-docs#28733. Sorry for the noise.

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.

1 participant