fluentui
fluentui copied to clipboard
microsoft
BasicList
💡 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
- [link to https://open-ui.org/]
- [x] Open GitHub issues related to component
- [link to each issue]
- [x] Create react-* package and component from template
- [link to package: https://github.com/microsoft/fluentui/tree/master/packages/react-components/react-(your-component)]
- [x] (Optional) Draft implementation
- [link to draft implementation, if applicable]
- [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
- [ ] Add tests
- [x] Unit and conformance tests
- [x] VR tests - N/A, The List itself doesn't have any visuals out of the box
- [x] #31656
- [x] #31659
- [x] Accessibility behavior tests
- [ ] Create an issue and run manual accessibility tests: [link to issue]
- [x] Validate with partners
- [x] Run a bug bash with other FUI crews
- [x] Finalize documentation
- [x] Review and add any missing storybook stories
- [x] 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
disallowedChangeTypesto"major", "prerelease"
- [ ] Ensure exports are removed from from
Leslie Kou is design contact for this. Lydia is contributing for Usage Guidance.
ADO Work Item. https://uifabric.visualstudio.com/iss/_sprints/taskboard/Fluent%20Core%20Design/iss/Design%20Horizontals/Fluent%20Core%20Design/2311%20-%20Nov?workitem=9684 https://uifabric.visualstudio.com/iss/_sprints/taskboard/Fluent%20Core%20Design/iss/Design%20Horizontals/Fluent%20Core%20Design/2312%20-%20Dec?workitem=9732 https://uifabric.visualstudio.com/iss/_sprints/taskboard/Fluent%20Core%20Design/iss/Design%20Horizontals/Fluent%20Core%20Design/2312%20-%20Dec?workitem=7694
📢 "Leslie is exploring the differences between BasicList and DataGrid with Sarah and the component club. The investigation process is ongoing, and the PM has pushed the end date to December. Jiri is testing components to see what engineering can accomplish."
📢
- "Leslie & Lydia are editing the Decision Tree and discussing what a spec would look like in defining what a List should do and the types of things contained within. They plan to repurpose some parts of DataGrid and discuss with Toshie."
- "Leslie & Lydia will work together on a Usage Guidance doc as a part of the spec, which will be shared with the Development team. The design team feels this will be ready for handoff to DEV in the new year and will have a more concrete update after the next few weeks."
- "Jiri is ready to demo the prototype/interactions and talk about some of the limitations he found."
@gouttierre - moving the ETA to Mar 2024 as the design spec is still not available
📢 "Brian scheduled a follow up for the designers and engineering to meet on the 30th." "Jiri is ready to demo the prototype/interactions and talk about some of the limitations he found."
📢 "@george-cz shared the prototype with the design team and created the PR for List shim. A regroup is scheduled between design and dev next week (12/12). Lydia and Leslie will share in-progress usage guidance that will include rough definition of what design thinks List should be and an updated decision tree."
📢
- Milan gave great feedback on the List accessibility questions after reviewing the meeting recording, so Leslie will be working with Lydia and Jiri to see how that works with the samples Jiri has built out.
📢 "Jiri has a new keyboard navigation pattern which takes inspiration from Treegrid and Datagrid. Jiri will schedule a meeting for some time this week to sync on progress"
📢
- Jiri demonstrated the accessibility roles and their limitations in different scenarios of grid / list navigation.
- He showed how the final navigation would work in various use-cases. The narrator for the grid / experience could be improved .
- The devs need to polish the code examples for the accessibility patterns and will speak with Sarah.
- Leslie will watch the recording
📢
- Leslie is going to take a stab at seeing what they can combine with their design-decision tree for one tree to rule them all. Since we're leading with usage guidance and examples, it would be helpful to have Lydia's help on this when she's back from vacation and ramped up.
- Jiri has shared a word document for it to be easier for Leslie to review the summary of Jiri's findings around different a11y features supported for different browser roles and supported behavior/roles for each use case: the desion tree- cc @george-cz
📢
- This week, Leslie will review the decision tree.
- Jiri, will continue working on the list documentation and include the selection and primary actions. Also, Jiri, will update everything to match the new changes.
- ODSP is interested in validating the component when in preview. cc @george-cz
📢
- Lydia and Leslie are making adjustments to the decision tree and usage guidance, then talking about what this means for the spec components.
- Jiri finishing up with the PR feedback, there is one thing that he needs to discuss with the team but is expecting to release the List for preview early next week
cc @george-cz , @tudorpopams, @JustSlone
📢
- Design said the behaviors are defined in the spec. (Leslie)
- Planning on going to unstable/ preview this week. There was a small last minute change to the API that needed review. (Jiri) cc @george-cz
📢
- Jiri has released preview ➡️ Storybook List
- Leslie will make some list items to help illustrate the Usage guidance and will have something to show Jiri by 4/23.
- Leslie will chat with Toshie about the list node (very useful for list work)
- ETA for Stable has been updated to EOF May from March. cc @george-cz
📢
- Per request from Design (Kari / Roma). List design work to be put on hold for 4-6 weeks so design (Leslie) can help another initiative due on the 15th of May.
- Teams (Ling) is aware of the request and mentioned that Teams can shift their ETA to uptake List component to June.
- Design must finish the design spec by May 30th at the latest. ⚠️Kari will check with Leslie this week and then Gouttierre will inform the comment / epic + team.
- The new ETA for List to be stable is June, until Design confirms it.
cc @george-cz, @ling1726, @tudorpopams , @miroslavstastny , @JustSlone
📢
- Engineering recently received some of the the final version of the spec from design.
- Due to priority changes in May w/ delays; the new ETA is at the end of July for stable since dev is not expecting much changes to be done.
cc @george-cz , @ling1726 , @tudorpopams , @JustSlone