FluentProvider to SelectFromSharePoint component so token is not undefined #2046
+276
−181
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
add world map control to docs nav
…es for improved theme handling and styling consistency
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
|
Thank you, @SeyedAliAsghari96 for the improvement! |
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.
…es for improved theme handling and styling consistency
What's in this Pull Request?
This PR introduces the use of FluentProvider to enable access to Fluent UI v9 design tokens within components.
Without wrapping components in FluentProvider, the tokens object returns undefined, causing styling inconsistencies.
By applying this change, theme handling is improved and styling remains consistent across light, dark, and high contrast modes.