SwiftFilesCombiner v1.1.0
We're excited to announce the release of SwiftFilesCombiner v1.1.0. This update brings new features and improvements to enhance the functionality and usability of our Swift file combining tool.
New Features
-
Current Directory as Default Input:
- If no directory path is provided as an argument, SwiftFilesCombiner now uses the current directory as the input.
- This feature allows for more flexible usage in various scenarios.
-
Improved Argument Handling:
- The tool now supports three usage patterns:
a) No arguments: Uses current directory and default output file name.
b) One argument: Uses current directory and specified output file name.
c) Two arguments: Uses specified directory and output file name.
- The tool now supports three usage patterns:
-
Default Output File Name:
- When no output file is specified, the tool defaults to "combined_swift_files.swift".
Improvements
-
Enhanced Error Handling:
- Better error messages for various scenarios, including directory not found and file write failures.
-
Code Refactoring:
- Implemented a protocol-based approach for file system operations, improving testability and maintainability.
-
Expanded Test Coverage:
- Added new test cases to cover edge scenarios and the new features.
Usage
swift SwiftFilesCombiner [<directory_path>] [<output_file>]
If no arguments are provided, the current directory will be used, and the output will be 'combined_swift_files.swift'.
Feedback and Contributions
We welcome your feedback and contributions. Please feel free to open issues or submit pull requests on our GitHub repository.
What's Next
We're continuously working to improve SwiftFilesCombiner. Some areas we're exploring for future releases include:
- Option to exclude specific files or directories
- Support for custom file extensions beyond .swift
Thank you for using SwiftFilesCombiner!