# Lists plan

Now plan:
- Update Thomas' hook PR - review and get a path forward
- Fluent UI team to help review, and communicate change with partners
- Subsequent PR will have surgical fixes for Strict Mode compliance
- Other strict mode work:
* [List](https://github.com/microsoft/fluentui/issues/14296): componentWillReceiveProps with paging-related updates
* [GroupedList](https://github.com/microsoft/fluentui/issues/14295): componentWillReceiveProps
* [GroupHeader](https://github.com/microsoft/fluentui/issues/14295): componentWillReceiveProps (simple)
* [DetailsRow](https://github.com/microsoft/fluentui/issues/14291): componentWillReceiveProps with selection state update

Questions we need to resolve:
- When, where, how does concurrent mode happen?
- in default version, either in-place or @fluentui/react-detailslist
- How can people continue to access the unmodified non-concurrent lists in v8?
- ~~FUR/detailslist (eventually FUR/detailslist/compat)~~
- not supported
- How can we help partners migrate?
- ~~post v8/v9 pickup lists/next or lists/ (when we're done)~~
- Think about this later but we won't need it now if we're not making API changes
- Where will Sebastian's new lists go and when/how will they be released?
- ... in v9?

Plan:

- Potentially a small amount of work to get details list strict mode compliant. Thomas can consult/help spend some time here.
- This is probably a minor
- Scaffold separate DetailsList package which contains concurrent version and unmodified compat version
- Look into this, maybe for v8
- Depends on these to be scaffolded first:
- `@fluentui/react-icon-utilities` - Icon, FontIcon, registerIcons
- `@fluentui/react-portal` - Layer moves here, we Portal and support but deprecate old name.
- `@fluentui/react-tooltip` - Tooltips
- Keep as much of API surface as possible in concurrent mode version (any removed things will be marked as deprecated in compat version as warning)
- Migration: Post-release of version 8, we'll add the `compat` paths (or compat package) to version 7 to help partners migrate.
- Think about this for button
- Not needed if we don't scaffold detailslist
- Sebastian's list will move in at some point under /next or different package (and start marking old APIs as deprecated)
- this is later

Next steps:
- Thomas looking back at PR to ship in minor (manual integration of changes since then)
- Try adding concurrent support (in place?)
- React-Redux's super-hack for StrictMode compliance: https://github.com/reduxjs/react-redux/commit/d16f759d727359fde3cc141cfc068fd13f184de8#diff-4a561361865a8e6d0758088bf7cded8d
- Github issues:
- [DetailsList](https://github.com/microsoft/fluentui/issues/14292): componentWillReceiveProps (complex)
- [List](https://github.com/microsoft/fluentui/issues/14296): componentWillReceiveProps
- [GroupedList](https://github.com/microsoft/fluentui/issues/14295) and related
- GroupedList: componentWillReceiveProps
- GroupHeader: componentWillReceiveProps
- [DetailsHeader and DetailsRow](https://github.com/microsoft/fluentui/issues/14291)
- DetailsHeader: findDOMNode
- DetailsRow: findDOMNode, componentWillReceiveProps