Fix init-windows template to automatically detect existing codegen spec files

[Copilot]

• Analyze the issue with hardcoded codegen includes in init-windows template
• Scan codegen directory for existing spec files during template generation
• Update template to use actual filenames when existing spec files are found
• Add fallback to conditional includes when no existing files are present
• Test the solution with existing projects
• Add explanatory comments about Mustache template syntax for C++ developers
• Run yarn change prerelease and yarn lint:fix
• Revert unrelated changes to FlatList file
• Fix Mustache template parsing error caused by example syntax in comments

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

Microsoft Reviewers: Open in CodeFlow

[anupriya13]

@copilot don't add a comment for developer to fix, we need to get the correct file name from..\codegen\<filename>.g.hfile

[Copilot]

@copilot don't add a comment for developer to fix, we need to get the correct file name from..\codegen\<filename>.g.hfile

I've updated the solution to automatically detect existing codegen spec files instead of using TODO comments. The template now:

1. Scans the windows/{projectName}/codegen/ directory for existing *Spec.g.h files during template generation
2. If existing spec files are found, uses the actual filename and extracted module name
3. Falls back to conditional __has_include checks when no existing files are found

This eliminates the need for manual developer intervention while handling both scenarios correctly. (commit b02696d)

[sundaramramaswamy]

LGTM!

[sundaramramaswamy]

LGTM

[sundaramramaswamy]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).

[anupriya13]

@copilot run yarn change prerelease and yarn lint:fix

[Copilot]

@copilot run yarn change prerelease and yarn lint:fix

Completed both tasks:

1. Generated prerelease change file with description "Fix init-windows template to automatically detect existing codegen spec files"
2. Fixed linting issues - corrected spacing in template.config.js and cleaned up FlatList file
   (commit e6f2c9f)

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• googlechromelabs.github.io
  • Triggering command: /usr/local/bin/node install.mjs (dns block)
• https://storage.googleapis.com/chrome-for-testing-public/130.0.6723.116/linux64/chrome-linux64.zip
  • Triggering command: /usr/local/bin/node install.mjs (http block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

[anupriya13]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).

[anupriya13]

@copilot fix pipeline issues for fabric

new windows\testcli\testcli.cpp
new windows\testcli\testcli.def
× Running init-windows...
Error: Error: Unclosed section "variable" at 1794. (90ms)
Command failed with error Unknown: Unclosed section "variable" at 1794
creaternwlib.cmd Done, see new cpp-lib project in D:\a_work\1\testcli with [email protected], [email protected], and [email protected]
##[error]Cmd.exe exited with code '-1'.
Finishing: Init

[Copilot]

@copilot fix pipeline issues for fabric

new windows\testcli\testcli.cpp...

Fixed the Mustache template parsing error. The issue was that the explanatory comments contained example Mustache syntax tags ({{#variable}}, {{^variable}}, {{/variable}}) which the template parser was trying to process as actual template code, causing the "Unclosed section 'variable' at 1794" error. Removed the example syntax from the comments while keeping the explanations. (commit 4f5620f)

[anupriya13]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).