fluentui
fluentui copied to clipboard
Rating
💡 When you create a PR for any of the checklist items, add a link to this Epic under the PR's Related Issues section.
Preparation
- [x] Open UI Research
- [x] Open GitHub issues related to component
- [x] Create react-* package and component from template
- [x] Draft implementation
- [x] Component Spec authored and reviewed
Implementation
- [x] Component implementation
- [x] Initial conformance and unit tests (validate basic functionality)
- [x] Initial documentation
- [x] Storybook stories
- [x] README.md covering basic usage
- [x] MIGRATION.md guide (include v8 and v0)
- [x] Component released as unstable from
@fluentui/react-components/unstable
Validation
- [x] Add tests
- [x] Unit and conformance tests: #30414
- [x] VR tests: #30414
- [ ] Bundle size fixtures
- [ ] Performance test scenario
- [x] Accessibility behavior tests
- [ ] Create an issue and run manual accessibility tests: #30471
- [ ] Validate with partners
- [ ] Run a bug bash with other FUI crews
- [ ] Finalize documentation
- [ ] Review and add any missing storybook stories
- [ ] Finalize migration guide
- [ ] Component released as stable from
@fluentui/react-components
- [ ] Ensure exports are removed from from
@fluentui/react-components/unstable
- [ ] In package.json: Remove the alpha/beta tag from the version number in package.json
- [ ] In package.json: Change beachball's
disallowedChangeTypes
to"major", "prerelease"
- [ ] Ensure exports are removed from from
📢"Tomi has a v1 ready to demo. He will put a meeting on our calendars to review it and go from there!"
📢 " @tomi-msft has shared a demo with version one on the teams chat. Folks on the chat are to review the demo for early feedback, and possibly set up a follow-up meeting with engineering and design.
Toshie to view Tomi's recording of demo and will connect async. Will need to do a spec review as well.
📢 "Most of the implementation is completed. Tomi has shared the demo. Toshie and folks are reviewing the demo to share feedback; followed with a spec review meeting which is scheduled for next week."
📢
- In preview
- Tomi made changes to the Rating Api based convos.
Rating
andRatingDisplay
. To split the component into two: One interactive component and another read only component, so that there is a clearer distinction on roles and stylings. RatingDisplay would be the read-only version, and Rating would be the interactive version. cc @tomi-msft , @behowell
📢
-
Tomi
has finished the next steps and is ready to collaborate with the partners on theRating
validation phase. PM to check with designers (Toshie), Geoff and then loop in engineering. cc @tomi-msft, @behowell, @GeoffCox
📢
- Teams will evaluate the Rating component with their adaptive card experiences. cc @tomi-msft