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

RFC appearance migration #24181

Merged
merged 20 commits into from
May 8, 2023
Merged

RFC appearance migration #24181

merged 20 commits into from
May 8, 2023

Conversation

petdud
Copy link
Contributor

@petdud petdud commented Aug 2, 2022

Current Behavior

Fluent V9 changes the default appearance of input components (Dropdown, Input, TextArea). V0 input components default background color is grey-ish, whereas in V9 the background color is white.

New Behavior

This RFC explores potential solutions for partners, so they could migrate input components to V9 without the extra work of adding an additional prop to input components.

Partners should also easily revert the decision to the default appearance value if they decide so, without changing inputs individually.

👀 PREVIEW

@github-actions github-actions bot added the Type: RFC Request for Feedback label Aug 2, 2022
@fabricteam
Copy link
Collaborator

fabricteam commented Aug 2, 2022

📊 Bundle size report

🤖 This report was generated against 347e2f68a22630b6de882ef032e5a42695b64774

@codesandbox-ci
Copy link

codesandbox-ci bot commented Aug 2, 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 913adc9:

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

@petdud petdud changed the title RFC Input appearance migration RFC appearance migration Aug 2, 2022
@size-auditor
Copy link

size-auditor bot commented Aug 2, 2022

Asset size changes

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

Baseline commit: c02b44a98770f8d9da499dbacadcf377eb5efb45 (build)

petdud and others added 6 commits August 4, 2022 11:09
Co-authored-by: Miroslav Stastny <mistastn@microsoft.com>
Co-authored-by: Miroslav Stastny <mistastn@microsoft.com>
Co-authored-by: Miroslav Stastny <mistastn@microsoft.com>
@miroslavstastny miroslavstastny requested review from a team August 23, 2022 13:00
@bsunderhus
Copy link
Contributor

IMO this should not have an impact in FluentUI, so it's a big no for New token alias to theme.

Both Composed component and Wrap the library components on application side seems like a bad idea for the Nova component, although both sound like sound choices for an application POV.

Global css selector sounds like a hack.

Unify design sounds like the way to go forward here, but it's no go for the design team 🙈.

I'm kind of thorn here 😅.
I'd still go for Composed component or Wrap the library components on application side, but I have no idea how to solve this for Nova

rfcs/convergence/apperance-migration.md Outdated Show resolved Hide resolved
rfcs/convergence/apperance-migration.md Outdated Show resolved Hide resolved
rfcs/convergence/apperance-migration.md Show resolved Hide resolved
rfcs/convergence/apperance-migration.md Show resolved Hide resolved
rfcs/convergence/apperance-migration.md Show resolved Hide resolved
rfcs/convergence/apperance-migration.md Show resolved Hide resolved
@layershifter
Copy link
Member

If we want to affect all components in a tree we can go only with "New token" or "CSS selector". I also proposed "React Context" option to determine defaults. IMO it has some benefits as it affects React's behavior.

miroslavstastny and others added 2 commits September 12, 2022 09:17
Co-authored-by: Oleksandr Fediashov <alexander.mcgarret@gmail.com>
@miroslavstastny
Copy link
Member

I also proposed "React Context" option to determine defaults.

Added pros and cons.

@msft-fluent-ui-bot
Copy link
Collaborator

Because this pull request has not had activity for over 150 days, we're automatically closing it for house-keeping purposes.

The pull request will still be available for reference. If it's still relevant to merge at some point, you can reopen or make a new version based on the latest code.

@msft-fluent-ui-bot msft-fluent-ui-bot added the Resolution: Soft Close Soft closing inactive issues over a certain period label Feb 12, 2023
@layershifter layershifter reopened this Feb 17, 2023
@miroslavstastny miroslavstastny requested a review from a team as a code owner May 8, 2023 21:25
@miroslavstastny
Copy link
Member

React context solution was implemented in #25262. The RFC has been updated to document the implemented solution.

@miroslavstastny miroslavstastny merged commit f5a38d3 into microsoft:master May 8, 2023
26 checks passed
marcosmoura added a commit to marcosmoura/fluentui that referenced this pull request May 10, 2023
* master:
  feat(react-drawer): create DrawerBody component (microsoft#27581)
  feat(react-tree): TreeItem itemType restructure (microsoft#27799)
  feat: Implement state management for toasts (microsoft#27800)
  bugfix: fix VisibleFlatTreeItemGenerator omitting visible items (microsoft#27802)
  fix: overflowManager should always dispatch initial state (microsoft#27756)
  fix(react-badge): Remove white border around presence badge when on a dark background (microsoft#27780)
  react-tags: rename dismissable to dismissible (microsoft#27798)
  chore: update ownership of react-tags (microsoft#27795)
  applying package updates
  feat(react-tags): Replace `avatar` prop with `media`; polish styles for spacing (microsoft#27725)
  RFC appearance migration (microsoft#24181)
  chore(react-skeleton): Release react-skeleton to stable (microsoft#27767)
  fix(Coachmark): Remove positioning regression and update bounds on resize (microsoft#27782)
  applying package updates
  fix(v8): explicitly publish dist folder after node 16 upgrade (microsoft#27769)
marcosmoura added a commit to marcosmoura/fluentui that referenced this pull request May 10, 2023
* feat/drawer-header:
  fix: add changefiles
  feat(react-drawer): create DrawerBody component (microsoft#27581)
  feat(react-tree): TreeItem itemType restructure (microsoft#27799)
  feat: Implement state management for toasts (microsoft#27800)
  bugfix: fix VisibleFlatTreeItemGenerator omitting visible items (microsoft#27802)
  fix: overflowManager should always dispatch initial state (microsoft#27756)
  fix(react-badge): Remove white border around presence badge when on a dark background (microsoft#27780)
  react-tags: rename dismissable to dismissible (microsoft#27798)
  chore: update ownership of react-tags (microsoft#27795)
  applying package updates
  feat(react-tags): Replace `avatar` prop with `media`; polish styles for spacing (microsoft#27725)
  RFC appearance migration (microsoft#24181)
  chore(react-skeleton): Release react-skeleton to stable (microsoft#27767)
  fix(Coachmark): Remove positioning regression and update bounds on resize (microsoft#27782)
  applying package updates
  fix(v8): explicitly publish dist folder after node 16 upgrade (microsoft#27769)
marcosmoura added a commit to marcosmoura/fluentui that referenced this pull request May 10, 2023
* master: (29 commits)
  feat(react-drawer): create DrawerBody component (microsoft#27581)
  feat(react-tree): TreeItem itemType restructure (microsoft#27799)
  feat: Implement state management for toasts (microsoft#27800)
  bugfix: fix VisibleFlatTreeItemGenerator omitting visible items (microsoft#27802)
  fix: overflowManager should always dispatch initial state (microsoft#27756)
  fix(react-badge): Remove white border around presence badge when on a dark background (microsoft#27780)
  react-tags: rename dismissable to dismissible (microsoft#27798)
  chore: update ownership of react-tags (microsoft#27795)
  applying package updates
  feat(react-tags): Replace `avatar` prop with `media`; polish styles for spacing (microsoft#27725)
  RFC appearance migration (microsoft#24181)
  chore(react-skeleton): Release react-skeleton to stable (microsoft#27767)
  fix(Coachmark): Remove positioning regression and update bounds on resize (microsoft#27782)
  applying package updates
  fix(v8): explicitly publish dist folder after node 16 upgrade (microsoft#27769)
  applying package updates
  fix: do not use outlineStyle: none in createCustomFocusIndicatorStyle (microsoft#26089)
  fix: Scale pulse animation with percentages and flip wave animation's direction (microsoft#27654)
  Publish dist folder that got removed due to node 16 upgrade (microsoft#27764)
  fix(scripts-update-release-notes): properly handle git for-each-ref cmd call to not fail release notes update (microsoft#27757)
  ...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution: Soft Close Soft closing inactive issues over a certain period Type: RFC Request for Feedback
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

9 participants