Problem
Because @fluentui/react-components does not always re-export all of the functionality of the sub-packages from which it is composed it can lack feature parity with its sub-packages.
For example, @fluentui/react-utilities provides a useMount() hook that is not re-exported from @fluentui/react-components meaning a user directly depending on react-utilities has access to more features than one depending on react-components.
Appetite
3~4 weeks. We should have a solution prior to the release of v9 stable at the end of June.
Solution
All features that are part of the public API of any of @fluentui/react-components' sub-packages should also be part of @fluentui/react-components' public API.
Risks (Rabbit holes)
Out of scope (No-gos)
- No breaking changes
Related
Problem
Because
@fluentui/react-componentsdoes not always re-export all of the functionality of the sub-packages from which it is composed it can lack feature parity with its sub-packages.For example,
@fluentui/react-utilitiesprovides auseMount()hook that is not re-exported from@fluentui/react-componentsmeaning a user directly depending onreact-utilitieshas access to more features than one depending onreact-components.Appetite
3~4 weeks. We should have a solution prior to the release of v9 stable at the end of June.
Solution
All features that are part of the public API of any of
@fluentui/react-components' sub-packages should also be part of@fluentui/react-components' public API.Risks (Rabbit holes)
Out of scope (No-gos)
Related