feat(command): Add Create Source/Header Pair command #840

anonchihaya0908 · 2025-07-16T06:08:54Z

Improves the C++ development workflow by providing a new command to create corresponding source and header files simultaneously, mirroring common IDE functionality.

This new command, clangd.createSourceHeaderPair, provides the following features:

Prompts the user for a valid C++ class name with robust validation.
Intelligently detects the target directory, preferring the active file's location.
Generates professional-grade file templates for both the header and source file.
Handles cross-platform line endings (EOL) correctly by respecting user settings.
Prevents accidental file overwrites by checking for existing files before creation.
Is accessible from the Command Palette and the editor context menu.

Resolves #839

Improves the C++ development workflow by providing a new command to create corresponding source and header files simultaneously, mirroring common IDE functionality. This new command, `clangd.createSourceHeaderPair`, provides the following features: - Prompts the user for a valid C++ class name with robust validation. - Intelligently detects the target directory, preferring the active file's location. - Generates professional-grade file templates for both the header and source file. - Handles cross-platform line endings (EOL) correctly by respecting user settings. - Prevents accidental file overwrites by checking for existing files before creation. - Is accessible from the Command Palette and the editor context menu. Resolves #[Your-Issue-Number-Here]

Refactored the PairCreator class to modularize logic for file name validation, language detection, template generation, file existence checks, and file writing. Added interfaces and constants for better type safety and maintainability. Improved user prompts and error handling, and made the code more extensible for both C and C++ file generation.

context-aware wizard, significantly improving user experience and flexibility. Key improvements include: - A single, multi-step input flow for all creation logic. - Dynamically sorts template choices based on the active language context (C vs. C++), prioritizing the most likely user intention. - Disambiguates between C and C++ structs, providing correct templates and file extensions for each. - Introduces intelligent, dynamic placeholders in the file name input box based on the current file and selected template. - The underlying code has been significantly refactored for clarity, maintainability, and type safety, breaking down complex logic into single-responsibility helper methods.

anonchihaya0908 · 2025-07-16T11:36:53Z

Hi

Following up on my previous comment, I took some time to explore the idea of context-aware support for both C and C++, and I'm excited to share the results.
I've just pushed a major update that fully implements this concept, creating what I believe is a much more robust and intuitive final version. Instead of a simple C++-only feature, it is now a unified creation wizard that intelligently adapts to the user's context.
Here are the key features of this new implementation:
Unified Template Selection: There is now a single, powerful wizard for all users.
Context-Aware UI: The list of choices (C Files, C++ Class, etc.) is dynamically sorted based on the active file's language, gently guiding the user towards the most logical option without restricting their freedom.
Disambiguated struct Support: The menu now clearly distinguishes between a C Struct (with typedef) and a C++ Struct, providing the correct template for each language's conventions.
Intelligent Placeholders: The file name prompt now suggests a smart default based on the current file's name and the chosen template type.
This addresses the C language support issue I raised earlier, and I believe it does so in a very flexible and user-friendly way. The underlying code has also been significantly refactored to support this new UI while maintaining high standards of quality.
This PR is now in its final state and is ready for a full review.
Thank you for your patience and for creating the space for this iteration. I'm very much looking forward to your feedback

Replaces the old template and file extension logic with a unified PairingRule structure, simplifying template selection and file generation for C and C++ header/source pairs. Improves language detection, user prompts, and file content generation, making the code more maintainable and user-friendly.

anonchihaya0908 · 2025-07-16T15:29:33Z

Added intelligent sorting logic for options and more precise expressions.

Temporarily locked.cpp/.h.

anonchihaya0908 · 2025-07-16T17:08:28Z

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 issue #839.

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!

Renamed 'createSourceHeaderPair' to 'newSourcePair' throughout the codebase and updated command titles for clarity. Added a new command for configuring source/header pairing rules. Improved template rule labels with icon syntax for better UI presentation. Created a placeholder for pairing rule service.

anonchihaya0908 · 2025-07-18T11:14:13Z

It's almost done, but the template issue still isn't resolved, and it can only generate .h type templates. Besides that, the code is pretty long due to a lot of templates and comments. If possible, can we break it down into separate files?

Split the monolithic create-source-header-pair.ts into separate files: coordinator.ts, service.ts, ui.ts, and templates.ts, and updated the module index and registration logic. Updated package.json command and configuration descriptions for clarity. Adjusted extension and command registration in extension.ts and updated pairing-rule-manager.ts as needed.

Refactored the coordinator to move directory and language detection to the service layer, streamlined the file creation flow, and added logic to offer saving custom C++ extension pairs as defaults. The UI now prompts for template type and file extensions in a more intuitive order, and success messages are shown non-blockingly. Service layer now provides file path creation and improved file existence caching.

Refactors the PairCoordinator to use dependency injection for service and UI layers, simplifying the workflow and improving testability. Moves file creation and rule-saving logic into the service layer, and moves workspace folder picking into the UI layer. Updates the registration logic to construct dependencies explicitly. Also, centralizes file extension selection UI in PairingRuleUI and cleans up related code.

Added an icon to the 'New Source/Header Pair' command and registered it in the explorer context menu for folders. This improves discoverability and usability of the command within the file explorer.

Deleted the clangd.newSourcePair command configuration from the package.json contributes.commands section. This cleans up unused or deprecated command definitions.

anonchihaya0908 · 2025-07-19T13:58:32Z

finished.

JVApen

See comments

JVApen · 2025-07-22T05:49:05Z

package-lock.json

vscode-nls seems to be deprecated: https://github.com/microsoft/vscode-nls

JVApen · 2025-07-22T05:59:19Z

package.json

See comment in bug, though I'd be more inclined to ask for a snippet ID rather than having fields to indicate a class/struct.

JVApen · 2025-07-22T06:02:40Z

package.json

I like your addition of relevant icons, though can you do this in a separate PR, such that it's easier to track the relevant changes and/or land these changes separately?

JVApen · 2025-07-22T06:03:50Z

src/ast.ts

 import * as vscodelc from 'vscode-languageclient/node';

 import {ClangdContext} from './clangd-context';
+


File is touched without any significant changes. Can you undo this newline? (Unless required by formatting rules)

JVApen · 2025-07-22T06:18:06Z

src/create-source-header-pair/service.ts

This contains a lot of code trying to find out which rule the user intended. Can't we delegate that to the user? If they add a 'label' as part of the configuration, they can have a rule for classes, structs, free functions or anything custom with the exact same extensions. They can than pick the intended entry from a list.

JVApen · 2025-07-22T06:31:02Z

vscode-clangd-fancy-0.2.1.vsix

Binaries should not be included

JVApen · 2025-07-22T06:31:26Z

package-lock.json

 {
-    "name": "vscode-clangd",
-    "version": "0.2.0",
+    "name": "vscode-clangd-fancy",


Please don't rename the project

anonchihaya0908 added 3 commits July 16, 2025 13:56

anonchihaya0908 added 2 commits July 16, 2025 20:54

Update create-source-header-pair.ts

605aab9

anonchihaya0908 added 3 commits July 16, 2025 23:51

Update create-source-header-pair.ts

1c0cfd9

Update create-source-header-pair.ts

9663d80

Update create-source-header-pair.ts

76e3d19

anonchihaya0908 mentioned this pull request Jul 16, 2025

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

Open

anonchihaya0908 added 4 commits July 17, 2025 16:06

npm run format

438f11a

fix

da3e288

fix

85adf58

anonchihaya0908 added 13 commits July 18, 2025 19:24

fix register.

475839e

npm run format

4345afc

npm run format

e6b97fe

Update ui.ts

aad7b7c

Update ui.ts

6ac7352

Update ui.ts

0d3e9dd

fuck

9c6135a

Add icon and explorer context menu for new source/header pair

a820052

Added an icon to the 'New Source/Header Pair' command and registered it in the explorer context menu for folders. This improves discoverability and usability of the command within the file explorer.

Remove clangd.newSourcePair command from package.json

c31a851

Deleted the clangd.newSourcePair command configuration from the package.json contributes.commands section. This cleans up unused or deprecated command definitions.

Update service.ts

21eeb6b

anonchihaya0908 added 5 commits July 19, 2025 16:13

Update package.json

1ccc7d9

Update coordinator.ts

2f7cb17

fix

173b431

Create vscode-clangd-fancy-0.2.1.vsix

7b9d7c0

Update service.ts

149d7c3

anonchihaya0908 added 4 commits July 19, 2025 22:18

Update service.ts

55cffa9

format

21eb998

Update package.json

fc34485

Update package.json

838165e

JVApen requested changes Jul 22, 2025

View reviewed changes

Merge branch 'clangd:master' into master

aac5797

		import * as vscodelc from 'vscode-languageclient/node';

		import {ClangdContext} from './clangd-context';

feat(command): Add Create Source/Header Pair command #840

Are you sure you want to change the base?

feat(command): Add Create Source/Header Pair command #840

Uh oh!

Conversation

anonchihaya0908 commented Jul 16, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

anonchihaya0908 commented Jul 16, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

anonchihaya0908 commented Jul 16, 2025

Uh oh!

anonchihaya0908 commented Jul 16, 2025

Uh oh!

anonchihaya0908 commented Jul 18, 2025

Uh oh!

anonchihaya0908 commented Jul 19, 2025

Uh oh!

JVApen left a comment

Choose a reason for hiding this comment

Uh oh!

JVApen Jul 22, 2025

Choose a reason for hiding this comment

Uh oh!

JVApen Jul 22, 2025

Choose a reason for hiding this comment

Uh oh!

JVApen Jul 22, 2025

Choose a reason for hiding this comment

Uh oh!

JVApen Jul 22, 2025

Choose a reason for hiding this comment

Uh oh!

JVApen Jul 22, 2025

Choose a reason for hiding this comment

Uh oh!

JVApen Jul 22, 2025

Choose a reason for hiding this comment

Uh oh!

JVApen Jul 22, 2025

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

anonchihaya0908 commented Jul 16, 2025 •

edited

Loading

anonchihaya0908 commented Jul 16, 2025 •

edited

Loading