microsoft / microsoft/react-native-windows
Re-export "@types/react-native" with forked props
Open
Nobody has claimed this yet.
Area: FlatList
Area: Focus
Area: Keyboard
Area: Mouse
enhancement
Workstream: Component Parity
- Dominant language
- C++
- Stars
- 17.3k
- Forks
- 1.2k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 33
Description
E.g. allow
Import-site
// Re-exported react-native FlatList with extra props
import {FlatList} from 'react-native-windows'
// For xplat, can alias
import {FlatList as FlatListWindows} from 'react-native-windows'
Types-site
...
import type {FlatListProps as VanillaFlatListProps} from 'react-native'
export type FlatListProps = VanillaFlatListProps & {
keepAreasRealized: RealizationConfig,
}
...
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how react-native-windows currently exports React Native components and their TypeScript declarations. Compare the proposed FlatList re-export and forked FlatListProps with the existing exports, then identify the type and runtime surfaces that would need to agree. Done means consumers can import the Windows component and its extended props as shown.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react-native, typescript
- Domain
- mobile-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100