microsoft / microsoft/react-native-windows

Unfork ComponentDescriptorRegistry.cpp

Open
#14,204 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Deforking enhancement Integration Follow-up Workstream: Component Parity
Dominant language
C++
Stars
17.3k
Forks
1.2k
Avg merge
1d 13h
Merged PRs (30d)
33

Description

Problem Description

Broke pages for Glyph UWP, Fabric Native Component, and Fabric Native Component Yoga. It looks like the removed the fallback if there's no component descriptor. Need to figure out if we want to make an upstream change to add these back in or change our implementation.

Image

Link to the integration where the error originated

https://github.com/microsoft/react-native-windows/pull/14167

Link to commit

https://github.com/facebook/react-native/pull/47321/files#diff-72b7ba7c6e256aefc85b580139f3023d60892ad5a74beb17754e4c786716cb6c

Forked files
  1. ComponentDescriptorRegistry.cpp
Upstream PR

No response

Build Configuration

None

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with ComponentDescriptorRegistry.cpp and compare the fork with the upstream commit linked in the issue. Check the affected Glyph UWP, Fabric Native Component, and Fabric Native Component Yoga pages using the integration from PR #14167. Done means the fallback behavior is restored through an agreed upstream or local change and those pages work.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, react-native
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.