microsoft / microsoft/fluentui-contrib
[Feature](react-headles-provider): migrate react-components imports to suite only
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 56
- Forks
- 62
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 1
Description
but shouldn't this be a dependency of react-components?
it is. wondering why it's used as direct sub-package import @layershifter ?
Some bits of API are not available through
@fluentui/react-components. We need to export them and update@fluentui-contrib/react-headless-providerto import only@fluentui/react-components.
Originally posted by @layershifter in #184
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the imports in @fluentui-contrib/react-headless-provider and the exports available through @fluentui/react-components. Identify the APIs currently imported from direct sub-packages, expose those APIs through @fluentui/react-components, and update the provider so it imports only from that package.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100