feat: expose theme enum and store to consumer #578
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
yhabib
approved these changes
Feb 9, 2025
AntonioVentilii
added a commit
to dfinity/oisy-wallet
that referenced
this pull request
Feb 10, 2025
# Motivation Bumping `@dfinity/gix-components` because we would like to use the theme features exposed in: - dfinity/gix-components#578
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.
Motivation
Some consumers, such as OISY, might want to implement their own theme toggler. Therefore to avoid conflicts with different themes, we expose the enum and store of the library for consumers as well (as we do with other stores).
Changes
Themeandtheme.store