taskcheck 1.5.0__tar.gz → 1.5.2__tar.gz

{taskcheck-1.5.0/taskcheck.egg-info → taskcheck-1.5.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: taskcheck
-Version: 1.5.0
+Version: 1.5.2
 Summary: Automatic scheduler for taskwarrior
 Requires-Python: >=3.11
 Description-Content-Type: text/markdown
@@ -32,7 +32,7 @@ Use it if you want to:
 - ✨ Auto-schedule tasks from working hours + calendar blocks
 - 🧭 Support complex working-hour maps
 - ⏱️ Consider urgency, due dates, and dependencies
-- 🧪 Dry-run mode to preview changes
+- 🧪 Persisted dry-run previews for reports and timelines
 - ↩️ Undo the latest schedule update
 - 🧠 Auto-adjust urgency when deadlines cannot be met
 - 🔄 Force-refresh iCal calendars
@@ -84,7 +84,9 @@ tuesday = [[9, 12.30], [14, 17]]
 - `taskcheck --timeline 1w` → automatic day/week/month timeline for the next week
 - `taskcheck --timeline eom --zoom week` → weekly timeline through month end
 
-Timeline rows follow dotted project levels such as `work.client`. Without `--zoom`, the most detailed view that fits the terminal width is selected: day, then week, then month. The track uses `▶` for a start, `━` for work, `◀` for an end, and `◆` for a deadline. Thin, heavy, and double rules separate days, weeks, and months. Project colors are deterministic and adapt to light or dark terminals when `COLORFGBG` is available.
+Create a preview with `taskcheck --schedule --dry-run`. It does not update Taskwarrior; instead, it saves the generated schedule to the Taskwarrior data directory. Reuse it with `taskcheck --report today --dry-run` or `taskcheck --timeline 1w --dry-run`.
+
+Timeline rows follow dotted project levels such as `work.client`. Without `--zoom`, the most detailed view that fits the terminal width is selected: day, then week, then month. The track uses `▶` for a start, `━` for work, `◀` for an end, and `◆` for a deadline. Thin, heavy, and double rules separate days, weeks, and months. Project colors are deterministic and adapt to light or dark terminals through OSC 11, with config and environment fallbacks.
 
 ## Reference
 

{taskcheck-1.5.0 → taskcheck-1.5.2}/README.md

@@ -17,7 +17,7 @@ Use it if you want to:
 - ✨ Auto-schedule tasks from working hours + calendar blocks
 - 🧭 Support complex working-hour maps
 - ⏱️ Consider urgency, due dates, and dependencies
-- 🧪 Dry-run mode to preview changes
+- 🧪 Persisted dry-run previews for reports and timelines
 - ↩️ Undo the latest schedule update
 - 🧠 Auto-adjust urgency when deadlines cannot be met
 - 🔄 Force-refresh iCal calendars
@@ -69,7 +69,9 @@ tuesday = [[9, 12.30], [14, 17]]
 - `taskcheck --timeline 1w` → automatic day/week/month timeline for the next week
 - `taskcheck --timeline eom --zoom week` → weekly timeline through month end
 
-Timeline rows follow dotted project levels such as `work.client`. Without `--zoom`, the most detailed view that fits the terminal width is selected: day, then week, then month. The track uses `▶` for a start, `━` for work, `◀` for an end, and `◆` for a deadline. Thin, heavy, and double rules separate days, weeks, and months. Project colors are deterministic and adapt to light or dark terminals when `COLORFGBG` is available.
+Create a preview with `taskcheck --schedule --dry-run`. It does not update Taskwarrior; instead, it saves the generated schedule to the Taskwarrior data directory. Reuse it with `taskcheck --report today --dry-run` or `taskcheck --timeline 1w --dry-run`.
+
+Timeline rows follow dotted project levels such as `work.client`. Without `--zoom`, the most detailed view that fits the terminal width is selected: day, then week, then month. The track uses `▶` for a start, `━` for work, `◀` for an end, and `◆` for a deadline. Thin, heavy, and double rules separate days, weeks, and months. Project colors are deterministic and adapt to light or dark terminals through OSC 11, with config and environment fallbacks.
 
 ## Reference
 

{taskcheck-1.5.0 → taskcheck-1.5.2}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "taskcheck"
-version = "1.5.0"
+version = "1.5.2"
 description = "Automatic scheduler for taskwarrior"
 readme = "README.md"
 requires-python = ">=3.11"

{taskcheck-1.5.0 → taskcheck-1.5.2}/taskcheck/__main__.py

@@ -4,6 +4,7 @@ from importlib.metadata import version
 
 from taskcheck.parallel import check_tasks_parallel
 from taskcheck.common import config_dir
+from taskcheck.dry_run import load_dry_run_results, save_dry_run_results
 
 arg_parser = argparse.ArgumentParser()
 arg_parser.add_argument("--version", action="version", version=f"taskcheck {version('taskcheck')}")
@@ -62,6 +63,7 @@ arg_parser.add_argument(
     help="Weight for urgency in scheduling (0.0 to 1.0), overrides config value. When 1.0, the whole Taskwarrior urgency is used for scheduling. When 0.0, the Taskwarrior urgency is reduced to only due urgency.",
 )
 arg_parser.add_argument(
+    "-d",
     "--dry-run",
     action="store_true",
     help="Perform scheduling without modifying the Taskwarrior database, useful for testing.",
@@ -151,6 +153,8 @@ def main():
             config,
             **check_tasks_kwargs,
         )
+        if args.dry_run and result is not None:
+            save_dry_run_results(result, taskrc=args.taskrc)
         print_help = False
 
     if args.report:
@@ -158,9 +162,8 @@ def main():
 
         config = load_config()
         scheduling_results = None
-        if args.schedule and args.dry_run:
-            # If we just did a dry-run schedule, use those results
-            scheduling_results = result
+        if args.dry_run:
+            scheduling_results = result if args.schedule else load_dry_run_results(args.taskrc)
         generate_report(
             config,
             args.report,
@@ -176,6 +179,8 @@ def main():
         from taskcheck.timeline import generate_timeline
 
         scheduling_results = result if args.schedule and args.dry_run else None
+        if args.dry_run and scheduling_results is None:
+            scheduling_results = load_dry_run_results(args.taskrc)
         zoom = getattr(args, "zoom", "day")
         if zoom not in {"auto", "day", "week", "month"}:
             zoom = "auto"

taskcheck-1.5.2/taskcheck/dry_run.py

@@ -0,0 +1,22 @@
+import json
+from pathlib import Path
+
+from taskcheck.undo import get_task_data_dir
+
+
+def get_dry_run_path(taskrc=None):
+    return get_task_data_dir(taskrc) / "taskcheck" / "dry-run.json"
+
+
+def save_dry_run_results(results, taskrc=None):
+    path = get_dry_run_path(taskrc)
+    path.parent.mkdir(parents=True, exist_ok=True)
+    path.write_text(json.dumps(results, indent=2, sort_keys=True))
+    return path
+
+
+def load_dry_run_results(taskrc=None):
+    path = get_dry_run_path(taskrc)
+    if not path.exists():
+        return None
+    return json.loads(path.read_text())

{taskcheck-1.5.0 → taskcheck-1.5.2/taskcheck.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: taskcheck
-Version: 1.5.0
+Version: 1.5.2
 Summary: Automatic scheduler for taskwarrior
 Requires-Python: >=3.11
 Description-Content-Type: text/markdown
@@ -32,7 +32,7 @@ Use it if you want to:
 - ✨ Auto-schedule tasks from working hours + calendar blocks
 - 🧭 Support complex working-hour maps
 - ⏱️ Consider urgency, due dates, and dependencies
-- 🧪 Dry-run mode to preview changes
+- 🧪 Persisted dry-run previews for reports and timelines
 - ↩️ Undo the latest schedule update
 - 🧠 Auto-adjust urgency when deadlines cannot be met
 - 🔄 Force-refresh iCal calendars
@@ -84,7 +84,9 @@ tuesday = [[9, 12.30], [14, 17]]
 - `taskcheck --timeline 1w` → automatic day/week/month timeline for the next week
 - `taskcheck --timeline eom --zoom week` → weekly timeline through month end
 
-Timeline rows follow dotted project levels such as `work.client`. Without `--zoom`, the most detailed view that fits the terminal width is selected: day, then week, then month. The track uses `▶` for a start, `━` for work, `◀` for an end, and `◆` for a deadline. Thin, heavy, and double rules separate days, weeks, and months. Project colors are deterministic and adapt to light or dark terminals when `COLORFGBG` is available.
+Create a preview with `taskcheck --schedule --dry-run`. It does not update Taskwarrior; instead, it saves the generated schedule to the Taskwarrior data directory. Reuse it with `taskcheck --report today --dry-run` or `taskcheck --timeline 1w --dry-run`.
+
+Timeline rows follow dotted project levels such as `work.client`. Without `--zoom`, the most detailed view that fits the terminal width is selected: day, then week, then month. The track uses `▶` for a start, `━` for work, `◀` for an end, and `◆` for a deadline. Thin, heavy, and double rules separate days, weeks, and months. Project colors are deterministic and adapt to light or dark terminals through OSC 11, with config and environment fallbacks.
 
 ## Reference
 

{taskcheck-1.5.0 → taskcheck-1.5.2}/taskcheck.egg-info/SOURCES.txt

@@ -3,6 +3,7 @@ README.md
 pyproject.toml
 taskcheck/__main__.py
 taskcheck/common.py
+taskcheck/dry_run.py
 taskcheck/google_calendar.py
 taskcheck/ical.py
 taskcheck/install.py

{taskcheck-1.5.0 → taskcheck-1.5.2}/tests/test_main.py

@@ -101,6 +101,9 @@ class TestArgumentParsing:
         args = arg_parser.parse_args(["--dry-run"])
         assert args.dry_run is True
 
+        args = arg_parser.parse_args(["-d"])
+        assert args.dry_run is True
+
         args = arg_parser.parse_args([])
         assert args.dry_run is False
 
@@ -413,10 +416,11 @@ class TestMainFunction:
                     auto_adjust_urgency=True,
                 )
 
+    @patch("taskcheck.__main__.save_dry_run_results")
     @patch("taskcheck.__main__.load_config")
     @patch("taskcheck.__main__.check_tasks_parallel")
     def test_main_schedule_with_dry_run(
-        self, mock_check_tasks, mock_load_config, sample_config, test_taskrc
+        self, mock_check_tasks, mock_load_config, mock_save, sample_config, test_taskrc
     ):
         """Test that dry-run mode returns scheduling results without modifying tasks."""
         mock_load_config.return_value = sample_config
@@ -437,6 +441,7 @@ class TestMainFunction:
             }
         ]
         mock_check_tasks.return_value = dry_run_results
+        mock_save.return_value = None
 
         with patch(
             "sys.argv",
@@ -469,6 +474,7 @@ class TestMainFunction:
         )
         mock_load_config.assert_called_once()
 
+    @patch("taskcheck.__main__.save_dry_run_results")
     @patch("taskcheck.__main__.load_config")
     @patch("taskcheck.__main__.check_tasks_parallel")
     @patch("taskcheck.report.generate_report")
@@ -477,6 +483,7 @@ class TestMainFunction:
         mock_generate_report,
         mock_check_tasks,
         mock_load_config,
+        mock_save,
         sample_config,
         test_taskrc,
     ):
@@ -499,6 +506,7 @@ class TestMainFunction:
             }
         ]
         mock_check_tasks.return_value = dry_run_results
+        mock_save.return_value = None
 
         with patch(
             "sys.argv",
@@ -536,6 +544,7 @@ class TestMainFunction:
             taskrc=test_taskrc,
             scheduling_results=dry_run_results,
         )
+        mock_save.assert_called_once_with(dry_run_results, taskrc=test_taskrc)
 
         # Verify that check_tasks_parallel was called with dry_run=True
         mock_check_tasks.assert_called_once_with(
@@ -548,6 +557,43 @@ class TestMainFunction:
             auto_adjust_urgency=True,
         )
 
+    @patch("taskcheck.__main__.load_dry_run_results")
+    @patch("taskcheck.__main__.load_config")
+    @patch("taskcheck.report.generate_report")
+    def test_main_report_dry_run_loads_cached_results(
+        self, mock_generate_report, mock_load_config, mock_load_cache, sample_config, test_taskrc
+    ):
+        mock_load_config.return_value = sample_config
+        cached = [{"id": "1", "scheduling": "2024-12-20 - PT2H"}]
+        mock_load_cache.return_value = cached
+
+        with patch("sys.argv", ["taskcheck", "--report", "today", "--dry-run", "--taskrc", test_taskrc]):
+            with patch("taskcheck.__main__.arg_parser.parse_args") as mock_parse:
+                mock_args = Mock()
+                mock_args.install = False
+                mock_args.schedule = False
+                mock_args.report = "today"
+                mock_args.timeline = None
+                mock_args.zoom = "auto"
+                mock_args.verbose = False
+                mock_args.force_update = False
+                mock_args.taskrc = test_taskrc
+                mock_args.urgency_weight = None
+                mock_args.dry_run = True
+                mock_args.auto_adjust_urgency = True
+                mock_parse.return_value = mock_args
+                main()
+
+        mock_load_cache.assert_called_once_with(test_taskrc)
+        mock_generate_report.assert_called_once_with(
+            sample_config,
+            "today",
+            False,
+            force_update=False,
+            taskrc=test_taskrc,
+            scheduling_results=cached,
+        )
+
     @patch("taskcheck.__main__.load_config")
     def test_main_config_loading_error(self, mock_load_config):
         """Test behavior when config loading fails."""