[DRAFT] Introduce a new cli command module-windows-setup

[anupriya13]

Description

Type of Change

• New feature (non-breaking change which adds functionality)
• Automation (AI changes or Github Actions to reduce effort of manual tasks)

Why

What is the motivation for this change? Add a few sentences describing the context and overall goals of the pull request's commits.

Resolves #15078

What

What changes were made to the codebase to solve the bug, add the functionality, etc. that you specified above.

Section A. Current Steps to integrate new arch windows template into a native module:

1. Create a TurboModule Spec File (js/ts) that lists all the APIs to be exposed by the library.
2. If Spec file already exists then refer that.
3. Update the package.json file with correct codegenConfig windows section with namespace, outputDirectory, etc.
4. Run “yarn react-native init-windows --template cpp-lib"
5. Update the .h and .cpp files with correct APIs defined in codegen/....g.h generated header file from spec file. The .h and .cpp main files should have all the APIs stubs defined that are defined in .g.h codegen file.
6. Implement those APIs

Section B. What are the issues?

• Generation of Spec file takes a lot of time going through ios and android implementations or windows paper APIs implementation then converting to js/ts turbo module spec file. Refer Native Platform: Native Modules · React Native for Windows and Native Modules: Introduction · React Native
• Creating Stub function .h and .cpp is manual (step 5) which can be automated. Currently it just adds multiply function.
• Init-windows also creates an example directory which has some issues currently.

Section C. How to make it easier?

• For Step 1 – we might want manual intervention on what APIs do we need in windows only add those APIs in TurboModule Spec File. This can be done separately using below copilot prompt:

convert this file to codegen spec file using turbomodule <ADD .H FILE CODE> refer below

// @flow 

import type { TurboModule } from 'react-native/Libraries/TurboModule/RCTExport'; 

import { TurboModuleRegistry } from 'react-native'; 

export interface Spec extends TurboModule { 

} 

export default (TurboModuleRegistry.get<Spec>('RNPrint'): ?Spec); 

• Automate steps 2 to 5 in section A using a single command from cli i.e. “yarn react-native module-windows-setup –logging"

• Step 6 is out of scope and can be done by developers

• Introduce a new flag --no-example in yarn react-native init-windows cli command that ignores the creation of example file directory. There can be cases where we don't want the example directory to be created on every init windows having a flag to ignore this would be very useful. Add --no-example flag to init-windows CLI command #15092

Screenshots

Add any relevant screen captures here from before or after your changes.

CLI.module-windows-setup.mp4

CLI with other APIs after generating spec file from prompt:

CLI.module-windows-setup.mp4

Testing

If you added tests that prove your changes are effective or that your feature works, add a few sentences here detailing the added test scenarios.

Optional: Describe the tests that you ran locally to verify your changes.

Changelog

Should this change be included in the release notes: yes

Add a brief summary of the change to use in the release notes for the next release.
Introduce a new cli command module-windows-setup