Custom Header Support #91
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
I implemented a new configuration field for a custom header override. If set, it will replace the regular Epitech header for the one set in the config and adapt it to fit the languages specifications.
The configuration is an array of string:
{ "epitech-c-cpp-headers.customHeader": [ "HEADER LINE 1", "HEADER LINE 2", "HEADER LINE 3", "..." ] }It also includes placeholders that will be replaced upon generation such as
%FILENAME%,%FILEPATH%,%PROJECTNAME%,%DESCRIPTION%More placeholders can be implemented in the future by editing the following:
https://github.com/IchiiDev/epitech-c-cpp-headers/blob/6ab07cb192afedccccd6c222da350c775d3f1f67/src/generators.ts#L61
Why ?
This can be useful for side projects where a header is wanted but the Epitech format doesn't feel right to use. Instead of using another extension, we can now override the default header and keep using the shortcuts and keybinds we are used to.