Add optional toast opacity support - #3
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.
What changed?
Added optional opacity support to ToastKit.
Developers can now make a toast translucent by calling
opacity():Calling
opacity()without a value uses0.8opacity. A custom value between0.0and1.0can also be provided:Opacity is completely opt-in. Toasts that do not use
opacity()continue to render normally with no change to their existing appearance or behavior.The feature works across Android and iOS and integrates with existing ToastKit features such as animations, presets, and toast updates.
Why?
This gives developers more control over the appearance of their toasts, making it possible to create softer or translucent toast styles without changing ToastKit's default appearance.
Existing applications are unaffected because opacity is only applied when explicitly requested.
How was it tested?
opacity()value of0.8.0.0and1.0.opacity()retain their existing appearance.Platforms tested
Breaking changes?
None.
Opacity is opt-in and does not change the appearance or behavior of existing toasts.
Checklist