* add Stylingcomponent doc
* add more info to doc
* fix wording and grammar
* added link for overriding tokens
* using customized with compose
* make edits to the style doc
* fix link in doc
* Update StylingComponents.md
fix link
* Fix link for overrides
---------
Co-authored-by: REDMOND\gulnazsayed <gulnazsayed@microsoft.com>
Made an update to the Accessing theme properties example, where it was not using the stock RN styling prop, and instead trying to use a color prop that doesn't exist on stock RN Text component.
* Move Text part of typography docs to Text README
* Change files
* Fix Markdown link
* Add reference to SPEC.md
Co-authored-by: Adam Gleitman <adgleitm@microsoft.com>
* Add font and typography documentation
* Text -> TextV1
* variants in typography object
* Add note on differences between TextV1 and V2 JSX types
Co-authored-by: Adam Gleitman <adgleitm@microsoft.com>
* Update global token documentation: make it not specific to color, add examples
* Remove font documentation
* Attempt to fix repo links - add ignore pattern for fluentui-design-tokens repo
* No additions, just rearranging documentation
Moved the different types of tokens to a new section, rearranged them in alphabetical order
* Add shadow documentation + some minor edits
* Respond to comments
* Bump all design-tokens packages to 0.29.0
* Update shadow naming
* Update font size naming (except Text)
* Update font size naming for Text
* Update naming for the color grey
* More shadow token naming updates
* Update line height naming + more font size naming updates
* Update stroke width token naming
* Forgot to save a color grey naming update
* More shadow renaming updates: missing .global, update comments
* Update snapshots affected by spacing rename
* Another shadow rename related change
* Split defaultColors.ts to fix brand color issues
* Update snapshots after previous commit
* Change files
* Bump design tokens packages from 0.29.0 to 0.31.0
* Update snapshots - no more undefined properties
All changes are related to the updated brand color ramp, there should be no other changes.
* Update corner radius tokens (the obvious ones - everything except large/extraLarge)
corner.radius.none -> corner.radiusNone
corner.radius.small -> corner.radius20
corner.radius.medium -> corner.radius40
corner.radius.circle -> corner.radiusCircular
* Update corner radius token naming (large/extra large), all in AvatarTokens
Used large -> 60 and extraLarge -> 80, based on the old win32 values.
The old values for mobile were large -> 80 and extraLarge -> 120
* Change files
* Forgot to save apple-theme/package.json
* This line got deleted by accident
* Update brand color ramp mapping
* Just grouping the colors we want to deprecate together, no changes to token definitions
* Update snapshots after updating brand color mapping
* update fluent-tester
* delete others
* move FluentTester src
* yarn build works
* rnx-bundle works
* autolinking bug workaround + android
* windows works
* Update Apple CI
* More CI updates
* Update more CI
* update
* more updates
* More updates
* Change files
* maybe fix android
* fix ci?
* fix ci?
* ci
* setup emulator
* Remove expander
* More fixes
* The final countdown
* more fixes
* fix more links
* derp
* Change files
* Rearrange jobs and more fixes
* JS PR back to top
* remove flag that doesn't work
* Update android bundle name, enable single app mode
* forgot some
* Remove extra space
* update lock
* Update CI
* Remove Drawer from Fluent tester for now
* remove drawer again
* Change files
* Fix metro configs
* rerun `yarn configure-test-app` and add back some more metro config changes
* no expander
* update react dep + fix pipeline maybe
* delete duplicate job
* update yarn lock
* add back rnta
* Change files
* Move new tests
* Fix bundle
* update links + Podfile + delete podfile locks temporarily
* remove drawer again, add back locks
* Update apps/fluent-tester/package.json
Co-authored-by: Tommy Nguyen <4123478+tido64@users.noreply.github.com>
* Update apps/win32/package.json
Co-authored-by: Tommy Nguyen <4123478+tido64@users.noreply.github.com>
* Update apps/fluent-tester/metro.config.js
Co-authored-by: Tommy Nguyen <4123478+tido64@users.noreply.github.com>
* updates
* back to windows-2019
* merge
* remove --use-nuget
* Update .ado/azure-pipelines.yml
* Add back auto-lauch packager to ios/macos
Co-authored-by: Tommy Nguyen <4123478+tido64@users.noreply.github.com>
* Replace some photos
* Replace some photos
* Rewrite some parts
* Some rewrite
* Better examples
* Small fixes
* Add more detail
* Edits
* Edits
* Edits
* Address feedback
### Platforms Impacted
- [x] iOS
- [x] macOS
- [x] win32 (Office)
- [x] windows
- [x] android
### Description of changes=
This PR moves the experimental button into the component button, as we are close to finishing the Button for V2. This PR will NOT be committed until messaging and the component has had final sign off from @ejlayne.
NOTE: It may be easier to review this commit-by-commit than all at once.
1. Old Button component is moved under a deprecated folder.
2. All experimental button files have been moved to the button package. The experimental button has been (temporarily) exported as `ButtonV2` to avoid name clashing with the already existing `Button`.
3. The experimental-button package now just reexports what it used to have from the button package. This is to minimize dropping changes we make to the V2 Button while migrating, and not have duplicate code.
4. Added deprecation messages to the experimental package and the old Button component:
- Experimental package will have the message "The @fluentui-react-native/exprimental-button package is deprecated. The contents of this package have been moved to @fluentui-react-native/button. If you need to use the Button component from this package, please use ButtonV2 from @fluentui-react-native/button."
- The old Button components will show in intellisense "This component is deprecated in favor of ButtonV2. This Button will be removed when the package moves to 1.0.0. At that point, ButtonV2 will be renamed to Button. Please see MIGRATION.md for details on how to move to the new Button."
5. I removed default exports for each control as I was worried that they would clash. This does not affect what gets exported from the package.
6. Merged the Button test pages for both buttons to one page. The old Button tests are now at the bottom of the Button test page. E2E tests have not been merged as I can't specify a test to look for more than two components.
### Verification
Verified that deprecation message only shows on debug, not release bundle
Verified that Button still loads out of experimental button. One test still pulls the button from the experimental-button package to ensure that it hasn't been broken.
Verified that deprecation intellisense shows up.
Verified that old Button is not affected via test page.
Verified E2E tests run on both versions of the button.
### Pull request checklist
This PR has considered (when applicable):
- [x] Automated Tests
- [x] Documentation and examples
- [ ] Keyboard Accessibility
- [ ] Voiceover
- [ ] Internationalization and Right-to-left Layouts
* Some edits
* migrating compose
* Change files
* Add link to migration documentation
* More details and exmaples
* More details
* Move file
* Add more details about component rename
* Change files
* Address feedback
* New pipeline to test if links on the repo are working
* Adding command
* Testing different path
* Parameter to fail test
* Reverting change
* Testing another fail condition
* Missing fail error
* Testing different test failure
* testing out xargs
* Fixing broken links to pass test
* Fix broken link
* Change name of config file
Co-authored-by: Krystal Kramer <krsiler@microsoft.com>
### Platforms Impacted
- [ ] iOS
- [ ] macOS
- [ ] win32 (Office)
- [ ] windows
- [ ] android
### Description of changes
Adding documentation for creating custom FURN themes.
Aim is to provide clear examples of how to add custom themes. Thanks to @FalseLobster for her examples in her AccChecker example, some of this documentation was modeled off of that example.
If there are use cases missing please let me know!
### Verification
Sending documentation to some partners as a test run
### Pull request checklist
This PR has considered (when applicable):
- [ ] Automated Tests
- [x] Documentation and examples
- [ ] Keyboard Accessibility
- [ ] Voiceover
- [ ] Internationalization and Right-to-left Layouts
* Reintroduced docs folder that was missing
* Specified fluentui to fluentui-react-native/docs
* Delete CONTROLS_STATUS.md
Not needed at the momment as theres no way to sync its information from the multiple sources of truth.
* Delete Pressable.mdx
* Delete Stack.mdx
* Delete counter.jsx
* Delete Text.mdx
* Removed docs not updated and fixed linking
* Removed JSX importing into MDX example
* Updated name from experimental to @fluentui/framework
* Divided theming more
* Moving to a new location
Moving this to the frameworks folder in packages
* list of docs from experimental moved to framework
* Added pages for future documentation on currently existing componenets/utilities
* Delete Seperator.mdx
* Added all componenets and utils to the index.mdx
* added missing .mdx extensions
Co-authored-by: Keven Arroyo <dake.3601@gmail.com>
Co-authored-by: sriya112 <sriyaaluru@gmail.com>
* Remove all docs content from fluentui-react-native
* add headline links to documentation
* update yarn.lock
* update yarn.lock for merge
* re-add images to new assets dir for repo readmes to reference
* refresh yarn.lock
* refresh yarn.lock cleanly after mege
* update yarn.lock
Co-authored-by: Chris Hogan <chrishog@microsoft.com>
* Revert "Merge pull request #136 from ksiler/fluent-variant-support"
This reverts commit fbbdcfe760, reversing
changes made to cf2dc6f865.
* Change files
Lawrence Win
Saad Najmi
lenahong
Lynn Zhang
E.J. Layne
Adam Gleitman
Ruriko Araki
Samuel Freiberg
Keven Arroyo
Nabil Khalil
Patrick Boyd
UI-Fabric-RN-Bot
Krystal Siler