You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
flowchart TB
A["new package"];
B["alpha release"]
C["beta/RC release"]
D["add to react-components unstable"]
DP["stories exposed to Docs"]
subgraph one["package release stage"]
A --> B --> C;
end
C -...-> D
subgraph two["package docs exposure"]
D --> DP
end
Loading
Scenario:
package is added to unstable/stable for react-components. We don't wanna render its stories in docsite
Proposal:
Introduce new package.json metadata field, with following API:
By default it will be false so the existing workflow will be a bit different. it will be package author responsibility to mark this to true once he is sure that stories can land in public docsite.
This can be automated as part of upcoming API propagation automation: nx workspace-generator add-package-to-react-components --name=@fluentui/new-package --access=unstable --docs
Have you discussed this feature with our team
v-build
Additional context
No response
Validations
Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
The text was updated successfully, but these errors were encountered:
Library
React Components / v9 (@fluentui/react-components)
Describe the feature that you would like added
Current component workflow is like following:
Scenario:
Proposal:
Introduce new
package.json
metadata field, with following API:By default it will be
false
so the existing workflow will be a bit different. it will be package author responsibility to mark this totrue
once he is sure that stories can land in public docsite.This can be automated as part of upcoming API propagation automation:
nx workspace-generator add-package-to-react-components --name=@fluentui/new-package --access=unstable --docs
Have you discussed this feature with our team
v-build
Additional context
No response
Validations
The text was updated successfully, but these errors were encountered: