* Introduce a sample-app-fabric
* Update the repo using yarn install
* Fix lint issues
* Enable Codeql alerts on the fabric app
* Fix lint using yarn
* Cleanup
* Fix test issues
---------
Co-authored-by: Jon Thysell <jthysell@microsoft.com>
* Doxysaurus tool to generate docs for C++
* Change files
* Fix spelling issue
* Exclude Doxysaurus templates from unbroken
* Update packages/@rnw-scripts/doxysaurus/src/test/string-template.ts
Co-authored-by: dannyvv <dannyvv@microsoft.com>
* Address some PR feedback
* Add CLI output option instead of DOCUSAURUS_DOCS var
* Update files per PR #6959
* Update comments and template extensions
* Reduce number of entries in .unbroken_exclusions
* Use path.resolve instead of ensureAbsolutePath
* Use the same version of mustache as other code
Co-authored-by: dannyvv <dannyvv@microsoft.com>
* Move office-iss packages to scope
Fixes#6937
The majority of packages in `packages` directory follow their package name, but @office-iss/react-native-win32 does not. Move the directory into a folder for scoped package, and move react-native-win32-tester along with it.
This also removes some stray gitignored files from react-native-wi32, so we clean up these outputs in vnext as well.
* Move warning earlier
* Change files
* CI fix
* Add workspace
* Fix
* metro config fix (and manually test this time)
* Rename E2ETest/e2etest to e2e-test-app
This is part of a series of PRs cleaning up naming in the `packages directory for consistency`. Certain conventions have grown over time, but not all packages follow them. This should create clarity on informal convnetions on where packages go and how to name them.
The changes across PRs
- `react-native-win32` and `react-native-win32-tester` to `@office-iss`
- `react-native-windows-codegen` to `@react-native-windows/codegen`
- `microsoft-reactnative-sampleapps to sample-apps`
- `E2ETest` to `e2e-test-app`
- `IntegrationTest` to `integration-test-app`
* Fix typo
* fix typos
* Rename microsoft-reactnative-sampleapps to sample-apps
This is part of a series of PRs cleaning up naming in the `packages directory for consistency`. Certain conventions have grown over time, but not all packages follow them. This should create clarity on informal convnetions on where packages go and how to name them.
The changes across PRs
- `react-native-win32` and `react-native-win32-tester` to `@office-iss`
- `react-native-windows-codegen` to `@react-native-windows/codegen`
- `microsoft-reactnative-sampleapps to sample-apps`
- `E2ETest` to `e2e-test-app`
- `IntegrationTest` to `integration-test-app`
* revert local state
* Reenable Appx signing
* trailing whitespace
* revert accidental deletion
* Move `react-native-windows-codegen` to `@react-native-windows/codegen`
This is part of a series of PRs cleaning up naming in the `packages directory for consistency`. Certain conventions have grown over time, but not all packages follow them. This should create clarity on informal convnetions on where packages go and how to name them.
The changes across PRs
- `react-native-win32` and `react-native-win32-tester` to `@office-iss`
- `react-native-windows-codegen` to `@react-native-windows/codegen`
- `microsoft-reactnative-sampleapps to sample-apps`
- `E2ETest` to `e2e-test-app`
- `IntegrationTest` to `integration-test-app`
* fix scoped bin
* Move some packages from @rnw-scripts to @react-native-windows
These are now being used by product code (e.g. @react-native-windows/cli). Move them to the versioning scheme and naming scheme of other product code, which will also let us backport a change dependent on using package utils.
* Change files