jettypod 4.2.2 → 4.2.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -196,10 +196,19 @@ sqlite3 .jettypod/work.db "SELECT id, title, scenario_file, mode FROM work_items
|
|
|
196
196
|
After reading the scenario file content, parse it to find the scenario this chore addresses:
|
|
197
197
|
|
|
198
198
|
1. Split the file by `Scenario:` to get individual scenarios
|
|
199
|
-
2.
|
|
199
|
+
2. Extract scenario titles from each block
|
|
200
|
+
3. Match the chore description to a scenario by:
|
|
200
201
|
- Looking for scenario numbers in the chore description (e.g., "Scenario 2")
|
|
201
202
|
- Matching keywords from the chore description to scenario titles
|
|
202
|
-
|
|
203
|
+
4. If no match found, list available scenarios and ask which one to implement
|
|
204
|
+
|
|
205
|
+
**Handle errors gracefully:**
|
|
206
|
+
- If no current work: "❌ No current work found. Run: jettypod work start <chore-id>"
|
|
207
|
+
- If no parent feature: "❌ Current work has no parent feature."
|
|
208
|
+
- If no scenario_file: "❌ Feature has no scenario_file. Create a scenario file and update the feature."
|
|
209
|
+
- If scenario file not found: "❌ Scenario file not found at [path]"
|
|
210
|
+
- If no scenarios in file: "❌ No scenarios found in scenario file."
|
|
211
|
+
- If can't match chore to scenario: List available scenarios and ask user which one
|
|
203
212
|
|
|
204
213
|
**Display to user:**
|
|
205
214
|
|