Repository navigation
docs: graduate dynamic colors to supported API - #38
Merged
Merged
Conversation
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.
Dynamic colors still carried experimental API annotations and only a short README description. Remove that designation and document the supported root exports and native behavior in a dedicated guide.
The guide covers installation and native rebuilding, platform availability, required and optional Material roles, read/notification semantics, cleanup, errors, and Ionic integration. README navigation links to it. App-local extensions retain their experimental status; runtime behavior and API signatures are unchanged.
Validation:
Companion theme documentation: webview-native-ui/ionic-theme-md3#68