microsoft / microsoft/react-native-windows
Migration documentation for removal of Glyph component in Fabric (only in Paper, Windows only non-core component)
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 17.3k
- Forks
- 1.2k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 33
Description
Summary
Similar to Flyout and Popup (Fabric tracking issue), there's a Windows-only component called Glyph which either needs to land on Fabric or be deprecated.
Glyph is not in the Gallery app, nor is it used in any samples.
Motivation
It would be work to replicate in Fabric. Before doing so let's see who its customers are, whether it needs to be inside RNW (vs. outside as a community module), and how it would map to RNW Fabric.
Basic Example
No response
Open Questions
No response
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 with the Glyph component documentation and the linked Fabric tracking issue. Identify whether Glyph has current customers, then document whether it should move into RNW Fabric, be deprecated, or live as a community module. Done means the customer impact and migration direction are recorded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react-native
- Domain
- desktop, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100