microsoft / microsoft/react-native-windows-samples

Add Native UI Component example using built-in control

Open
#301 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Engineering Improvement Candidate enhancement samples
Dominant language
C#
Stars
544
Forks
218
PR merge metrics
No merged PRs in 30d

Description

Proposal: Add a sample implementation of a Native UI Component that uses a built-in control

Summary

Currently, the docs for Native UI Components uses a fully custom control. It would be nice to have an example to show how developers can integrate existing UI controls instead of writing their own.

Motivation

As a React developer who is new to Windows development, it is unclear which portions of the existing sample are required if I'm using an existing XAML control. For instance, if I wanted to add a Command bar, do I need to create a class that extends from Control? Do I need to create a class for each different XAML tag type for Command bar? Having a through-yet-understandable example demonstrating a complex XAML control would be a great resource for developers to begin building out React versions of Windows UI components.

Open Questions

  1. Which XAML component should the sample use?

Additional Comments

I'm willing to contribute this documentation provided someone can point me in the right direction (particularly how to handle in JSX components that have nested XAML components).

Contributor guide

No contributing guide indexed for this repository

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 the existing Native UI Components documentation and its fully custom control sample. Choose a built-in XAML control such as Command bar, determine how nested XAML components are represented in JSX, and provide a complete understandable sample showing which parts are required.

Written by the indexing model from the issue text.

Assessment

Tech stack
react-native
Domain
desktop, documentation
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.