Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: move all stories from react-components package to public-docsite-v9 and remove storybook setup from suite package #31440

Merged

Conversation

Hotell
Copy link
Contributor

@Hotell Hotell commented May 21, 2024

Previous Behavior

  • official documentation lives within suite package ( legacy reasons no longer valid )

New Behavior

Based on previous discussion within v-build group:

public-docsite-v9

  • uses v9 eslint preset + fixes issues
  • all react-components stories are part to public-docsite-v9 app
  • adds jest testing setup
  • updates all public facing docs that use forbidden/obsolete api imports (@griffel/react , @fluentui/react-components/unstable )

react-components suite

  • no longer contains storybook setup as it's only purpose is re-export bucket from v9 stable packages
  • assets/ folder is removed as it's no longer relevant

Related Issue(s)

@github-actions github-actions bot added this to the April Project Cycle Q1 2024 milestone May 21, 2024
@Hotell Hotell changed the title Type checking perf/apply/suite storybook move chore: bring in all stories from react-components package to public-docsite-v9 and remve storybook setup from suite package May 21, 2024
@Hotell Hotell changed the title chore: bring in all stories from react-components package to public-docsite-v9 and remve storybook setup from suite package chore: bring in all stories from react-components package to public-docsite-v9 and remove storybook setup from suite package May 21, 2024
@fabricteam
Copy link
Collaborator

fabricteam commented May 21, 2024

📊 Bundle size report

✅ No changes found

@fabricteam
Copy link
Collaborator

fabricteam commented May 21, 2024

Perf Analysis (@fluentui/react-components)

No significant results to display.

All results

Scenario Render type Master Ticks PR Ticks Iterations Status
Avatar mount 655 609 5000
Button mount 295 322 5000
Field mount 1162 1112 5000
FluentProvider mount 723 736 5000
FluentProviderWithTheme mount 76 86 10
FluentProviderWithTheme virtual-rerender 37 35 10
FluentProviderWithTheme virtual-rerender-with-unmount 79 75 10
MakeStyles mount 874 870 50000
Persona mount 1767 1707 5000
SpinButton mount 1388 1411 5000
SwatchPicker mount 1524 1513 5000

Copy link

codesandbox-ci bot commented May 21, 2024

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

@Hotell Hotell force-pushed the type-checking-perf/apply/suite-storybook-move branch from 36d819e to aa921c6 Compare May 22, 2024 14:59
@Hotell Hotell changed the title chore: bring in all stories from react-components package to public-docsite-v9 and remove storybook setup from suite package chore: move all stories from react-components package to public-docsite-v9 and remove storybook setup from suite package May 22, 2024
@Hotell Hotell marked this pull request as ready for review May 22, 2024 15:49
@Hotell Hotell requested review from a team as code owners May 22, 2024 15:49
@Hotell Hotell force-pushed the type-checking-perf/apply/suite-storybook-move branch from d500877 to 682c17d Compare May 22, 2024 17:19
@Hotell Hotell force-pushed the type-checking-perf/apply/suite-storybook-move branch from 682c17d to e091b33 Compare May 28, 2024 12:24
@Hotell Hotell merged commit daa441d into microsoft:master May 28, 2024
20 checks passed
@Hotell Hotell deleted the type-checking-perf/apply/suite-storybook-move branch May 28, 2024 13:52
miroslavstastny pushed a commit to miroslavstastny/fluentui that referenced this pull request Jun 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants