The "src" directory contains a number of JS files that are added to the base copy of RN. It is not a complete source tree itself. Renaming to "patches" would increase clarity of intent, and follow OSS "patch-package" conventions.

What would you like to be added:

Adding a binding to a BindingBase property from the XAML should unwrap the binding expression.

For which Platform:

• iOS
• Android
• WebAssembly
• WebAssembly renderers for Xamarin.Forms
• Windows
• Build tasks
• Solution Templates

Anything else we need to know?

This check should also validate for `Binding

Describe the bug
Adding a reference to a ClassLibrary project from a UWP application project generates a XAML compiler warning.

Steps to reproduce the bug

1. Open Visual Studio 2019 (or 2017)
2. Create a new Universal Windows Class Library project
3. Create a new Universal Windows Application project in the same solution
4. Add a reference to the Class Library project from the Appl

Hello,

when I go to the "Share Single" category in the documentation, I realize that there is a list of applications supported by the react-native-share package.

So, to start with, I was already wondering what "Share Single" meant exactly. I didn't really understand the associated example gifs.

Then, why are some applications, like FACEBOOK_STORIES, only supported on iOS and others only