Skip to content

Conversation

@behowell
Copy link
Contributor

@behowell behowell commented Aug 4, 2022

@behowell behowell self-assigned this Aug 4, 2022
@github-actions github-actions bot added this to the July Project Cycle Q3 2022 milestone Aug 4, 2022
@fabricteam
Copy link
Collaborator

fabricteam commented Aug 4, 2022

📊 Bundle size report

Unchanged fixtures
Package & Exports Size (minified/GZIP)
react-components
react-components: Accordion, Button, FluentProvider, Image, Menu, Popover
187.656 kB
51.96 kB
react-components
react-components: FluentProvider & webLightTheme
33.359 kB
11.004 kB
react-portal-compat
PortalCompatProvider
5.851 kB
1.964 kB
🤖 This report was generated against e95ba37f3a8155930542712bfc63055c306cce56

@codesandbox-ci
Copy link

codesandbox-ci bot commented Aug 4, 2022

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.

Latest deployment of this branch, based on commit 1366cb6:

Sandbox Source
@fluentui/react 8 starter Configuration
@fluentui/react-components 9 starter Configuration

@fabricteam
Copy link
Collaborator

fabricteam commented Aug 4, 2022

Perf Analysis (@fluentui/react-components)

No significant results to display.

All results

Scenario Render type Master Ticks PR Ticks Iterations Status
Avatar mount 1259 1273 5000
Button mount 936 937 5000
FluentProvider mount 1480 1460 5000
FluentProviderWithTheme mount 571 578 10
FluentProviderWithTheme virtual-rerender 538 537 10
FluentProviderWithTheme virtual-rerender-with-unmount 573 589 10
MakeStyles mount 1973 1939 50000
SpinButton mount 2292 2341 5000

@size-auditor
Copy link

size-auditor bot commented Aug 4, 2022

Asset size changes

Size Auditor did not detect a change in bundle size for any component!

Baseline commit: f97dc9f0f713bdf845cdd250d3b2d2993a0a5a0d (build)

@behowell behowell force-pushed the field/add-to-react-components branch from f0c2cdd to e134d83 Compare September 8, 2022 18:01
@behowell behowell changed the title Add Field to react-components/unstable feat: Add *Field components to react-components/unstable Sep 8, 2022
@behowell behowell changed the title feat: Add *Field components to react-components/unstable feat: Publish react-field package, and export from react-components/unstable Sep 8, 2022
@behowell behowell marked this pull request as ready for review September 8, 2022 18:19
@behowell behowell requested review from a team as code owners September 8, 2022 18:19
@@ -0,0 +1,7 @@
{
"type": "minor",
Copy link
Member

@layershifter layershifter Sep 8, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This probably should be patch as it's an unstable feature.

@@ -0,0 +1,7 @@
{
"type": "patch",
Copy link
Member

@layershifter layershifter Sep 8, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

patch will trigger 9.0.0 release, it is okay of do you want to stay in alpha for now (i.e. use prerelease)?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've changed it to prerelease. Not sure why yarn change didn't default to that for an alpha package...

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ahh it looks like I need to change the disallowedChangeTypes to allow prerelease and disallow patch. (I wonder if that should be the default configuration from the create-package script?)

@layershifter
Copy link
Member

image

  • Please add/remove "Best practices"
  • Please a notice like in other preview components
    image

image

It seems that grouping is not correct as I would expect to have these stories on Field's page rather than separate links.

@behowell
Copy link
Contributor Author

behowell commented Sep 8, 2022

@layershifter

It seems that grouping is not correct as I would expect to have these stories on Field's page rather than separate links.

It is intentional, although I'd be happy to change it to make it clearer. There is no component named Field: those first stories are common field features, and the actual *Field components have their own documentation pages below that, with the props listed, and a default example.

I'm open to suggestions how best to document these features in the storybook. Perhaps there could be a single markdown page that describes the general Field features (rather than stories across several pages). And/or these stories could be repeated to each Field type.

@@ -1,5 +1,4 @@
import descriptionMd from './FieldDescription.md';
import bestPracticesMd from './FieldBestPractices.md';
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

#24735 tracks adding this back once the best practices have been written.

@layershifter
Copy link
Member

@layershifter

It seems that grouping is not correct as I would expect to have these stories on Field's page rather than separate links.

It is intentional, although I'd be happy to change it to make it clearer. There is no component named Field: those first stories are common field features, and the actual *Field components have their own documentation pages below that, with the props listed, and a default example.

I'm open to suggestions how best to document these features in the storybook. Perhaps there could be a single markdown page that describes the general Field features (rather than stories across several pages). And/or these stories could be repeated to each Field type.

I don't have a good suggestion, so I think that we can proceed as is and apply changes based on feedback. WDYT?

@behowell behowell enabled auto-merge (squash) September 12, 2022 18:18
@behowell behowell merged commit cd8f5a1 into microsoft:master Sep 12, 2022
@behowell behowell deleted the field/add-to-react-components branch September 12, 2022 18:59
marcosmoura added a commit to marcosmoura/fluentui that referenced this pull request Sep 14, 2022
* master: (28 commits)
  Fix value font-weight inside heatmap chart (microsoft#24726)
  Fix legend overflow-indication-text role (microsoft#24756)
  Support custom locale in date axis  (microsoft#24753)
  Cleanup env variables (microsoft#24739)
  ci(github): add GH Action to add issue labels based on new GH issue template (microsoft#24788)
  Update disallowedChangeTypes for newly created packages, to allow only 'prerelease' change types by default (microsoft#24763)
  feat(react-components): Adding missing AvatarGroup exports (microsoft#24770)
  remove unnecessary nohoist (microsoft#24760)
  feat(react-dialog): supports 1st rule of ARIA (microsoft#24525)
  BREAKING: TableCell layouts are handled by layout components (microsoft#24762)
  feat: Implement table cell layout components (microsoft#24773)
  applying package updates
  fix: remove readonly from DetailsList (microsoft#24615)
  chore: Cleaning up tokens in Button components so they better adhere to the design spec (microsoft#24732)
  fix: react-combobox listbox popup width matches trigger width (microsoft#24733)
  fix: react-combobox Option focus outline only shows with keyboard nav (microsoft#24700)
  feat: Publish react-field package, and export from react-components/unstable (microsoft#24235)
  fix: Replacing bottom border styles with text decoration underline in Link (microsoft#24734)
  docs(react-theme): Update readme (microsoft#24755)
  Add tests for hover states (microsoft#24390)
  ...
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.

feat: Add react-field to react-components/unstable

4 participants