feat: Customizable tmpo export Path
#57
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Introduces an 'export_path' option to both global and project config, allowing users to specify a default export directory for time entries. The export command now respects this setting, expanding '~' to the home directory and ensuring the directory exists before exporting. Updates config prompts and display to include the export path.
Updated the export path prompt to clarify that pressing Enter keeps the current value. Added instructions and logic to allow users to type 'clear' or 'none' to remove the export path setting.
Now shows '(current directory)' when export path is empty, providing clearer feedback to users about the export path location.
Introduces an optional export path field to the project initialization flow and configuration template. Updates the interactive prompt, config file generation, and related tests to handle the new export path option.
Add documentation for the new 'export path' setting in the configuration wizard, global config, and per-project `.tmporc` files. Explain how to set, clear, and override the export path, including priority and home directory expansion. Update usage examples and configuration field references accordingly.
DylanDevelops
changed the title
tmpo export Path
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Pull Request Checklist
mainbranch of tmpo.Closes #54
Description
This pull request introduces support for configuring a default export directory ("export path") for exported files, both globally and per-project. Users can now set, clear, or override the export path via the interactive configuration wizards, and documentation has been updated to explain this new feature. The export logic is updated to respect the export path, including support for
~home directory expansion and proper fallback behavior.Key changes include:
Feature: Export Path Configuration
ExportPathfield to both the global (GlobalConfig) and project (Config) configuration structs, along with corresponding YAML and template updates. [1] [2] [3] [4]tmpo config) and project init (tmpo init) commands to prompt for export path, display current/exported values, and handle clearing or skipping the setting. [1] [2] [3] [4] [5] [6]~, ensure the directory exists, and use it as the file output location. [1] [2] [3]Documentation Updates
README.md,docs/configuration.md, anddocs/usage.mdto document the new export path setting, its priority, usage examples, and how to set or clear it. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11]Code Quality and Testing
Minor Improvements
tmpo initfor better UX.These changes together make it easier for users to control where their exported files are saved, both globally and per-project, with clear documentation and robust handling in the CLI.