Chris Glein

We have Playground available as a stopgap example, but we should beef up the documentation for this on the website and/or samples repo.

Document only gives the context of "string". Yeah, that could give any detail and it'd be better.

Could be structured in the docs under some "tools" section that covers both VS and VSCode. But it sounds like this scenario requires full VS, and is specific to Chakra.

Looks like there's type information missing for APIs there, like the one you mentioned. It's unclear if the docs have a stale snapshot, of if we're missing the export. In...

@stmoy I know you coordinated a scrub of API docs recently. Was that just the native APIs? This one still isn't showing up.

First step is to catalog them. Not all will survive (for example upcoming changes to mouse/keyboard APIs), but we need to know what's there and decide how to document their...

@NickGerleman That page basically just tells you to run it in a VM. Is that not going to work with the move to ARM64? If not... what _is_ the solution?...

Agreed. It pretty unceremoniously drops you into a specific API: https://microsoft.github.io/react-native-windows/docs/flyout-component Which is what the Facebook docs do, but theirs are more comprehensive.

Correct string for Windows should be "windows". Not sure what the macOS one is. Should be able to look at what `Platform.OS` reports.

We need documentation about RNW's support level for opting into the new architecture.