API Extractor
API Extractor generates an api.md file containing the public API for a package. @fluentui/react and related packages as well as @fluentui/web-components use API Extractor to ensure that API changes must be reviewed before being merged into master. (@fluentui/react-northstar and related packages do not use API Extractor as of writing.)
As part of a package's build process, the api-extractor task checks the package's public API with the package's auto-generated .api.md file.
If building locally, the API file will be updated automatically (in 7.0 and master). Be sure to commit the updates with your other changes!
In PR builds, the task will fail if it detects missing API file updates.
(Previously it was necessary to run a separate command yarn update-api to update the API files, but we decided to streamline this and do the update automatically as part of the build instead.)
See the API Documentation page.
- FAQ - Fabric and Stardust to Fluent UI
-
@fluentui/reactVersion 9 -
@fluentui/reactVersion 8 - Contributing to the
7.0branch - How to apply themes (version 7/8)
- Planning and development process (for work by the core team)
- Conducting meetings Style guide
- Keeping up with review requests
- RFC review process
- Setup (configuring your environment)
- Fluent UI React version 7/8
- CLA
- Overview
- Repo structure
- Development process
- Contributing to previous versions
- API Extractor
- Build command changes made in early 2020
- Component implementation guide
- Creating a component
- Implementation Best Practices
- Theming
- Documenting
- Styling (old approach)
- Overview
- Testing with Jest
- E2E testing (Cypress)
- Visual testing (Screener)
- Accessibility review checklist