- fix #127
- you can now add a glob to ´ignoreFiles` in .ftsettings.json to skip files that should not be created by the extension
- fix #109
- added the ability to interpolate the current Date.
- fix #124
- If you use the command from the command palette or by keybind the extension will try to get the currently focused folder in VSCode explorer view and use that as target for template creation.
- fix #125
- The extension should now behave correctly and not automatically open files that were just created. Only if you specified that in the
filesToOpen
property of the .ftsettings.json file.
- The extension should now behave correctly and not automatically open files that were just created. Only if you specified that in the
- Introduced
setExecutablePermission
to ftsettings.json to allow automatic executable permissions if the template file was executable as well. - globalTemplatePath setting can now use a
%HOME%
placeholder which resolves to current users Home directory.
- Requires VSCode version 1.75.0
- Added support for custom template annotation
- No longer copy .DS_Store files on macOS. Thanks tjunxin
- Regression fix: Empty lines at the start and end of files will be kept again.
- The function to trim file and folder names was placed wrongly and due to that also trimmed file content.
- New Feature: Prepending/Appending to existing files is now possible. see the Examples
- fix a bug where losing when the inputbox lost focus the extension would move on as if the input was finished.
- fix a bug where pressing escape would not stop the creation process.
- fix a bug where the extension would allow invalid folder names by having spaces at the start or end of the names
- fix bug that would show "$ref" warnings in all kinds of json files
- Customizable global template directory (it is recommended to do this)
- If your global templates were deleted when you updated the extension this is due to a major mistake I made. I hope I fixed it but it still can't be guaranteed. Please choose a custom directory for your global templates so this won't happen again.
- DEPRECATED: The default Global Template directory will not be used anymore at some point in the future. So doing this sooner rather than later is encouraged.
- Thanks hondzik
- Added the option so templates can use an absolute path
- Fixed an issue where the extension would crash when no replace value is used
- Thank you very much ThumNet
- added an option to open specific files automatically when template creation is done.
- added '&' operator to support chaining transformers in a filename
- fixed json schema reference for settings file
- Changed Readme a bit more (I really need to get into writing better and easier to understand docs)
- fixed json schemapath for vscode settings.json
- added the possibility to configure the template folder path.
- added a static replace, replacefirst and replacelast function
-fixed .ftsettings.json schema
- Added
overwriteExistingFiles
property to structure settings
- Added Multifolder workspace support
- Fixed a bug where you couldn't have projects on a drive other than your system drive
- Added Extension Icon
- Thanks for all of these mrelemerson
- Added several new transformers.
- Added functionality to chain transformers
- Updated Docs
- fixed display error in inputbox when a customvariable has a defaultvalue
- added omitFTName option
- Fixed
Open Global Folder Template Directory
Command
Some breaking changes, I'm really sorry but I wanted to do this right and had to do it earlier rather than later. This will hopefully be the last breaking change
-
BREAKING: The
FFSName
Placeholder no longer works. Please replace it with the new placeholderFTName
-
BREAKING: Configuration namechange. Please switch the configuration keys from
fastFolderStructure.structures
tofolderTemplates.structures
andfastFolderStructure.fileTemplates
tofolderTemplates.fileTemplates
. -
BREAKING: Calling the
FFS.createFolderStructure
command will no longer work. Please replace it withFT.createFolderStructure
-
REMOVED: Creating a Template from an existing folder is no longer supported because you can now save templates on the filesystem.
-
ADDED: Reading Folder Templates from your File System. You can now choose where to create your templates. In the config file or as a Folder on the File System.
-
ADDED: You can now define defaultvalues for your customvariables with the new
variablename=>defaultvalue
notation.
Also added an examples folder.
- You can now pass in your own path argument with keybinds.
-
BREAKING: Removed default structures and fileTemplates as they are generally not useful for anyone due to everyone having their own needs. You have to create your own templates now.
-
If you create a template from an existing folder this extension will now save the new Template in your global or workspace settings. This depends on if you already have a workspace settings file with a template in it or not.
- Fix bug that filepaths weren't normalized when parent directory is ommited
- Added Create Template from Folder function
- Added Remove Template function
- Added
omitParentDirectory
flag - Added
snakecase
andkebabcase
transformers. Thanks Torben
- Added transformer
lowercasefirstchar
- Fixed
camelcase
transformer to lowercase the first char if it was uppercase - Fixed a bug where deleting a newly created structure and then creating it again skipped files
- NO BREAKING CHANGES
- Yippieh. I feel as if the extension is stable enough for its first major release 1.0.0. Hopefully this didn't jinx it.
- Added tests
- No longer overwrites existing files
- Added transformer
camelcase
andpascalcase
- Added possibility to configure Custom Variables
- reverted some changes to fix behaviour
- fixed a bug where you couldn't create multiple empty Directories
- added an
EmptyDirectory
keyword
- Added feature to transform your FFSName to lowercase, uppercase or capitalize it.(Thanks marcocavanna!)
- Cleaned up the readme a bit
- Added feature to automatically save files that have a template assigned. No more manually saving every file.
- Moved 'Create Folder from FFS-Template' Context Item into the workspace group where it should be.
Fixed wrong information in Readme on how to use the extension. Thank you snigglewhoop for pointing that out!
I forgot to test some stuff and broke the whole thing. It's working again.
Added info where this idea came from.
Fixed readme stuff
This is the super beta so people can't shout at me when something doesn't work.
You're glad you had those release notes, eh?