Rating

[TristanWatanabe]

💡 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

• Open UI Research
• Open GitHub issues related to component
• Create react-* package and component from template
  • link to package
• Draft implementation
  • link to draft implementation
• Component Spec authored and reviewed

Implementation

• Component implementation
• Initial conformance and unit tests (validate basic functionality)
• Initial documentation
  • Storybook stories
  • README.md covering basic usage
  • MIGRATION.md guide (include v8 and v0)
• Component released as unstable from @fluentui/react-components/unstable
  • Release Rating as Preview

Validation

• Add tests
  • Unit and conformance tests: Add unit and vr tests to Rating #30414
  • VR tests: Add unit and vr tests to Rating #30414
  • Bundle size fixtures
  • Performance test scenario
  • Accessibility behavior tests
  • Create an issue and run manual accessibility tests: Rating: Manual Accessibility Review Checklist #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"

[gouttierre]

📢"Tomi has a v1 ready to demo. He will put a meeting on our calendars to review it and go from there!"

[gouttierre]

📢 " @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.

[briandrouin]

Toshie to view Tomi's recording of demo and will connect async. Will need to do a spec review as well.

[gouttierre]

📢 "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."

[gouttierre]

📢

• In preview
• Tomi made changes to the Rating Api based convos. Rating and RatingDisplay. 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

[gouttierre]

📢

• Tomi has finished the next steps and is ready to collaborate with the partners on the Rating validation phase. PM to check with designers (Toshie), Geoff and then loop in engineering. cc @tomi-msft, @behowell, @GeoffCox

[gouttierre]

📢

• Teams will evaluate the Rating component with their adaptive card experiences. cc @tomi-msft

[gouttierre]

📢

• Design said the UI kit is not done yet. (Toshie)
• Component released to stable Rating (Tomi)