Skip to content

fix(react-headless-components-preview): export useContextValues for components requiring context in render functions#36300

Merged
dmytrokirpa merged 3 commits into
microsoft:masterfrom
dmytrokirpa:fix/headless-components-context-values-exports
Jun 11, 2026
Merged

fix(react-headless-components-preview): export useContextValues for components requiring context in render functions#36300
dmytrokirpa merged 3 commits into
microsoft:masterfrom
dmytrokirpa:fix/headless-components-context-values-exports

Conversation

@dmytrokirpa

Copy link
Copy Markdown
Contributor

Description

This PR ensures that all headless components with render functions accepting context as the second parameter properly export their useContextValues hooks.

Components Fixed

  • Dropdown - export useDropdownContextValues
  • Provider - export useProviderContextValues
  • Rating - export useRatingContextValues
  • RatingDisplay - export useRatingDisplayContextValues
  • Field - export useFieldContextValues
  • TabList - export useTabListContextValues
  • Accordion components:
    • Accordion - export useAccordionContextValues
    • AccordionHeader - export useAccordionHeaderContextValues
    • AccordionItem - export useAccordionItemContextValues

Why?

Components with render functions like renderDropdown(state, contextValues) require consumers to provide context values when calling the render function directly. These useContextValues hooks were already implemented but not exported, breaking the API contract for direct render function usage.

Changes Made

  • Added missing useContextValues exports at component-level index files
  • Added missing useContextValues exports at package-level entry points
  • No breaking changes to existing APIs

…t in render functions

- Dropdown: export useDropdownContextValues
- Provider: export useProviderContextValues
- Rating: export useRatingContextValues
- RatingDisplay: export useRatingDisplayContextValues
- Field: export useFieldContextValues
- TabList: export useTabListContextValues
- Accordion components: export context values hooks

These components have render functions that accept context as the second parameter, so the useContextValues hooks must be exported for consumers to create context values when calling render functions directly.
@dmytrokirpa dmytrokirpa marked this pull request as ready for review June 11, 2026 09:07
@dmytrokirpa dmytrokirpa requested a review from a team as a code owner June 11, 2026 09:07
@dmytrokirpa dmytrokirpa self-assigned this Jun 11, 2026
@dmytrokirpa dmytrokirpa requested review from Hotell and mainframev June 11, 2026 09:07
@github-actions

Copy link
Copy Markdown

Pull request demo site: URL

@github-actions

Copy link
Copy Markdown

📊 Bundle size report

Package & Exports Baseline (minified/GZIP) PR Change
react-headless-components-preview
react-headless-components-preview: entire library
199.535 kB
57.049 kB
199.802 kB
57.09 kB
267 B
41 B

🤖 This report was generated against 7786a3225f3b7108552a5b1aa0da27359966e5c1

@dmytrokirpa dmytrokirpa enabled auto-merge (squash) June 11, 2026 09:39
@dmytrokirpa dmytrokirpa changed the title fix: export useContextValues for headless components requiring context in render functions fix(react-headless-components-preview): export useContextValues for components requiring context in render functions Jun 11, 2026
@dmytrokirpa dmytrokirpa merged commit 3566735 into microsoft:master Jun 11, 2026
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants