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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I dig a bit deeper and it looks like that
const context = React.useContext(DocsContext);withinFluentDocsPage.storiesdoesn't work at all - it has no context property. To properly fix this we should fix the issue over there as this is moreless stateless component that is being set by parent.More context:
DocsContext.globalsexposes only following mapThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
quickly looking at others custom controls we have and it seems we might not have another option.
TOCis doing the same thing.Let's remove
{ selectedThemeId?: string }prop API fromThemePickeras its not being set anyways and handle it internally.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually the theme property is set in the global context after the emit, but because we can't really listen to those changes in an elegant way we still neet that
selectedThemeIdprop. This makes the dropdown keep the same value when switching from one component to another (ie change the theme on<Button>, then click on<CompoundButton>).There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it is set, but DocsPage wont get those values from globals thus this code doesn't do anything
This is the change I had in mind + applying your changes in this PR

There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So what I mean is that the
FluentDocsPageexample whereThemePickerpasses thatselectedTheme.idvalue to the prop is actually working after theaddons.getChannel().emit('updateGlobals', { globals: { [THEME_ID]: themeId } });call. This is the mechanism we use to keep the theme name consistent in the dropdown when changing pages.