Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Figure out how to deal with community native modules and WinUI 3 support #9136

Closed
Tracked by #9601
asklar opened this issue Nov 16, 2021 · 1 comment
Closed
Tracked by #9601

Comments

@asklar
Copy link
Member

asklar commented Nov 16, 2021

Write up strategy for modules to either dual target, or convert to winappsdk.
Needs to also consider how winappsdk vs. UWP is surfaced in reactnative.directory.

@ghost ghost added the Needs: Triage 🔍 New issue that needs to be reviewed by the issue management team (label applied by bot) label Nov 16, 2021
@chrisglein chrisglein added Area: Native Modules Area: WinUI enhancement Needs: Dev Design Platform: WinAppSDK and removed Needs: Triage 🔍 New issue that needs to be reviewed by the issue management team (label applied by bot) labels Nov 22, 2021
@chrisglein chrisglein added this to the 0.69 milestone Nov 22, 2021
@jonthysell
Copy link
Contributor

@asklar Is this still something that makes sense for 0.69 or should it be moved to 0.70?

@chrisglein chrisglein modified the milestones: 0.69, 0.70 Jun 6, 2022
@chrisglein chrisglein modified the milestones: 0.70, Backlog Jul 18, 2022
@chrisglein chrisglein closed this as not planned Won't fix, can't repro, duplicate, stale Sep 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

No branches or pull requests

4 participants