[soroshsabz]

Motivation

IntelliSense support for C++20 modules importing (#6302) is still in development on the language server side. Meanwhile, module-based projects already exercise extension-side behavior that currently has no test coverage:

• module interface files (.cppm/.ixx) being recognized as C++ sources,
• compile_commands.json entries containing GCC module flags (-fmodules-ts, -fprebuilt-module-path, -fmodule-file) not preventing IntelliSense,
• module-related compiler arguments (both GCC and MSVC spellings) surviving the custom configuration provider path unmodified.

This PR adds a CppModulesProject test scenario that locks that behavior in. It makes no statement about the semantic understanding of module imports by the language server — when server-side support lands, these tests are the natural place to add the end-to-end module IntelliSense assertions.

What the tests cover

1. File classification — .cppm/.ixx files open with the cpp language id (guards the file associations that module files depend on for any IntelliSense at all).
2. compile_commands.json with GCC module flags — a runtime-generated compile_commands.json (with the fake gcc checked into the scenario assets, following the SimpleCppProject pattern) carries the GCC module flags for an importer and two module interface units; IntelliSense reaches IntelliSenseReady for the importer.
3. Custom configuration provider — a v6 provider returns configurations carrying GCC-style (-fmodules-ts, -fprebuilt-module-path=..., -fmodule-file=...) and MSVC-style (/ifcSearchDir, /reference, /headerUnit, /stdIfcDir) module arguments; the tests assert the configurations are accepted/delivered and the files become ready. The extension-side handling that carries the MSVC modules workaround around has regressed before (the /ifcSearchDir//reference processing regression discussed in Add IntelliSense for C++20 modules importing #6302), so this is worth guarding.

Notes

• No product behavior change — tests and CI wiring only.
• CI: one new Windows step (yarn test --scenario=CppModulesProject) mirroring the existing SimpleCppProject step. Happy to drop it or extend it to other platforms per maintainer preference.
• Context: the engine-side prerequisite for gcc-dialect modules is progressing in the now-open EDG front end (C++20 modules: support gnu emulation modes and extended floating-point types edgcpp/compiler#315 fixes IFC generation in gnu emulation modes); this scenario is the extension-side acceptance harness for when that support reaches the shipped binaries.

Related: #6302

[Copilot]

🟡 Changes recommended

The tests do not establish compilation-database use or preservation of delivered module arguments.

2 open findings

• Readiness test does not verify compilation database usage · New
• Tests assert provider state instead of delivered configuration · New

What changed in this PR

Adds C++20 modules test groundwork for extension-side behavior while semantic module-import support remains under development.

Changes:

• Adds file-classification, compilation-database, and custom-provider tests.
• Adds module fixtures and fake compiler assets.
• Runs the scenario in Windows CI.

File	Description
Extension/​test/​scenarios/​CppModulesProject/​tests/​modules.integration.test.ts	Adds module scenario tests.
Extension/​test/​scenarios/​CppModulesProject/​assets/​math.ixx	Adds geometry module interface.
Extension/​test/​scenarios/​CppModulesProject/​assets/​math.cppm	Adds math module interface.
Extension/​test/​scenarios/​CppModulesProject/​assets/​main3.cpp	Adds MSVC-provider importer.
Extension/​test/​scenarios/​CppModulesProject/​assets/​main2.cpp	Adds GCC-provider importer.
Extension/​test/​scenarios/​CppModulesProject/​assets/​main.cpp	Adds compilation-database importer.
Extension/​test/​scenarios/​CppModulesProject/​assets/​bin/​gcc.exe	Adds Windows fake compiler.
Extension/​test/​scenarios/​CppModulesProject/​assets/​bin/​gcc	Adds non-Windows fake compiler.
Extension/​test/​scenarios/​CppModulesProject/​assets/​.gitignore	Ignores generated configuration files.
.github/​workflows/​job-compile-and-test.yml	Adds Windows scenario execution.

🧠 Review effort: Balanced

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Copilot]

🟢 Approval recommended

Static review identified no unresolved blocking issues in the test-only scenario, fixtures, or CI wiring.

1 open issue

• Tests assert provider state instead of delivered configuration

1 resolved since last review

• Readiness test does not verify compilation database usage

_{Review effort: Balanced}

[Copilot]

🟢 Approval recommended

The test-only changes follow existing scenario patterns, with no unresolved blocking findings.

No open issues 🎉

1 resolved since last review

• Tests assert provider state instead of delivered configuration

_{Review effort: Balanced}

[soroshsabz]

Sean McManus (@sean-mcmanus) Is there anything else I can do?

[soroshsabz]

As you can see edgcpp/compiler#315 has been merged

So please review this PR, I want to submit another PR for implement required features

[soroshsabz]

Sean McManus (@sean-mcmanus)

[soroshsabz]

Sean McManus (@sean-mcmanus) Could you run CI for this PR?

thanks

[Sean McManus (sean-mcmanus)]

soroshsabz My apologies -- I am and have been super busy recently.

[soroshsabz]

Sean McManus (@sean-mcmanus) Ok, I am waiting for you