[Feature Request] Add "Create Source/Header Pair" Command

[anonchihaya0908]

Hello,

Thank you for your excellent work on this extension.

Summary

To improve the C++ development workflow, I propose adding a new command: Create Source/Header Pair. This feature would allow users to create a .h and .cpp file simultaneously from a single class name, similar to the functionality found in IDEs like CLion.

The Problem (User Story)

Currently, when starting a new class, a developer has to perform several manual steps, which is repetitive and slows down the development flow. Separately, the existing Switch Between Source/Header command fails silently if the corresponding file doesn't exist, creating a dead end in the user's workflow.

Proposed Solution

I suggest a new command, clangd.createSourceHeaderPair, with the title "Create Source/Header Pair". When executed, it would:

1. Prompt the user for a class name (e.g., MyClass).
2. Intelligently determine the target directory (preferring the directory of the active file, otherwise falling back to the workspace root).
3. Create two files in that directory:
   • MyClass.h (with a basic header template).
   • MyClass.cpp (with the corresponding include and implementation stubs).
4. Automatically open the newly created header file in the editor for immediate use.

This command would be accessible from both the Command Palette and the editor's context menu.

##### Synergy with Existing Features

Crucially, this new command lays the groundwork for enhancing the existing Switch Between Source/Header command (Alt+O).

In a future enhancement, we could modify the Switch command's behavior:

• Current: When switching from foo.cpp and foo.h does not exist, nothing happens.(Didn't find a corresponding file.)
• Proposed: When foo.h does not exist, the extension could prompt the user: "Header 'foo.h' not found. Would you like to create it?"
• If the user agrees, it would then leverage this new file-creation logic.

This would transform a simple file-switching utility into a seamless, IDE-like workflow for both navigating and creating files.

Demo

Here is a short video demonstrating the initial "Create Source/Header Pair" command:

Future Enhancements

As mentioned, the primary enhancement is the synergy with the Switch command. Additionally, I have considered supporting more file extensions (e.g., .hpp, .cc), which could be made user-configurable in the settings. For now, this initial proposal focuses on establishing the core functionality.

Contribution

I have already implemented the standalone Create Source/Header Pair command, and the code aligns with the project's existing style. It is ready for review.

If this proposal is something you would consider for the extension, I am happy to open a Pull Request immediately for this foundational piece.

Thank you for your time and consideration. I look forward to your feedback.

[anonchihaya0908]

Just wanted to post a final summary of what this PR currently accomplishes and what I see as potential next steps, based on all the great feedback and discussion in pr #840 .

What this PR delivers:

• A new command, "Create Source/Header Pair," accessible from the command palette and context menu.
• A multi-step wizard UI that allows users to choose the type of content they want (Class, Struct, Empty, etc.).
• The wizard is context-aware: it intelligently reorders the template choices based on whether the user is in a C or C++ file.
• It includes robust features like input validation, file existence checks, platform-aware EOL handling, and smart placeholder generation.
• Crucially, it correctly infers the language context for .h files by checking for companion .c source files, solving a key usability issue.

Current Limitations & Future Work:

• Hardcoded Extensions: As a focused first step, this implementation currently creates only .h/.cpp or .h/.c pairs. The logic for user-configurable extensions (like .hpp or .cc) is something I've planned as a clear follow-up enhancement in a separate PR.
• Complex Project Structures: The context detection relies on finding companion files in the same directory. A future improvement could be to support more complex structures (e.g., src/ and include/ folders), potentially by leveraging compile_commands.json or other project-level information.

I believe this PR, in its current state, provides a solid and valuable foundation. Thank you again for all the guidance. I'm looking forward to your review!

[JVApen]

I'm a bit worried about inserting a lot of content in a new file. I understand the idea behind it, though I'm worried about all the options needed to make the content fit. For example: pragma once instead of/next to header guards, licenses, namespace(s), enum/struct/class, casing of class names.

We currently use https://marketplace.visualstudio.com/items?itemName=Gruntfuggly.auto-snippet#:~:text=This%20extension%20automatically%20inserts%20a,placeholders%20and%20regular%20expressions%2C%20etc.

This runs a VS Code snippet when a file is created. (https://code.visualstudio.com/docs/editing/userdefinedsnippets)
The snippet itself can also be ran using it's prefix (for example: cpp init).
It might be worth documenting some snippet examples. That way, we should only worry about creating the matching file at the right location.

[anonchihaya0908]

Hello @JVApen

First of all, thank you very much for your time and consideration in reviewing this pull request.

After submitting this PR, I continued to explore and develop the ideas within it. As the feature set grew, I came to a deeper understanding of the vscode-clangd extension's core philosophy. I now realize that the full scope of what I was building features beyond the core mission of the official extension. I completely understand and respect the need for the official plugin to remain focused, lean, and highly aligned with the language server's primary functions.

Therefore, I've decided to channel these efforts into a separate, dedicated "Power Tools" extension named Clotho. This new extension aims to complement the official vscode-clangd plugin by providing advanced, workflow-oriented features for C++ developers.

For anyone in the community who might find these tools useful, here are the links:

• GitHub Repository: this

Given this new direction, please feel free to close this PR at your convenience.
Thank you again for creating such a foundational and essential tool for the C++ community.

[JVApen]

I'm not saying this is out-of-scope, though due to the nature of the extension it should be usable for a broad audience. Hence the suggestion to use the snippets instead of hardcoding them.

I was really looking forward to having the switch header/implementation create a new file and/or create both files at once.

If you rather have your own workflow handled by a custom extension that's off course also an option.
You can also add the generic part here and configure it the way you like from your extension.

[anonchihaya0908]

That's a fantastic suggestion! I completely agree that leveraging user snippets is a much more flexible and robust approach.

I'll get right on it. I plan to have a new, refactored PR ready for your review by the end of this weekend.
Please do not close this pull request yet.
Thank you for the excellent guidance!