Conversation
@halo-dev/api-client
@halo-dev/components
@halo-dev/richtext-editor
@halo-dev/ui-shared
@halo-dev/ui-plugin-bundler-kit
commit: |
|
This branch has not been deployed
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.



What type of PR is this?
What this PR does / why we need it:
Add capability summaries to the Console theme detail page:
A new theme capabilities endpoint supplies template information and route patterns resolved from the current site configuration. Template descriptions and routes use a single frontend lookup, and route patterns are displayed as plain text. Existing settings tabs remain the entry point for theme settings.
Which issue(s) this PR fixes:
Refs #10044
This draft covers themes only; plugin detail improvements remain out of scope.
Special notes for your reviewer:
Implemented with LLM assistance: Codex for the backend and Claude Code for the frontend. Full review is pending.
Validation:
Does this PR introduce a user-facing change?