microsoft / microsoft/fluentui
Picker Recipes
Open
Nobody has claimed this yet.
Area: Components
Component: Pickers
Fluent UI react-components (v9)
Resolution: Soft Close
Type: Epic
- Dominant language
- TypeScript
- Stars
- 20.3k
- Forks
- 2.9k
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 46
Description
💡 When you create a PR for any of the checklist items, add a link to this Epic under the PR's Related Issues section.
Preparation
- Open UI Research
- [link to https://open-ui.org/]
- Open GitHub issues related to component
- [link to each issue]
- Create react-* package and component from template
- [link to package: https://github.com/microsoft/fluentui/tree/master/packages/react-components/react-(your-component)]
- (Optional) Draft implementation
- [link to draft implementation, if applicable]
- Component Spec authored and reviewed
Implementation
- Component implementation
- Initial conformance and unit tests (validate basic functionality)
- Initial documentation
- Storybook stories
- README.md covering basic usage
- MIGRATION.md guide (include v8 and v0)
- Component released as unstable from
@fluentui/react-components/unstable
Validation
- Add tests
- Unit and conformance tests
- VR tests
- Bundle size fixtures
- Performance test scenario
- Accessibility behavior tests
- Create an issue and run manual accessibility tests: [link to issue]
- Validate with partners
- Run a bug bash with other FUI crews
- Finalize documentation
- Review and add any missing storybook stories
- Finalize migration guide
- Component released as stable from
@fluentui/react-components- Ensure exports are removed from from
@fluentui/react-components/unstable - In package.json: Remove the alpha/beta tag from the version number in package.json
- In package.json: Change beachball's
disallowedChangeTypesto"major", "prerelease"
- Ensure exports are removed from from
Contributor guide
No contributing guide indexed for this repository
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 with the linked Component Implementation Guide and the Open UI Research step, then review the react-(your-component) package template. The checklist spans implementation, conformance and unit tests, Storybook stories, README.md, MIGRATION.md, validation, and package.json release changes. Done means every preparation, implementation, validation, and release checkbox is addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- documentation, frontend, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100