Task 3: Step 2 complete - plan sub-tasks for bug fixes
Build and Publish Mana Loop Docker Image / build-and-publish (push) Successful in 6m42s
Build and Publish Mana Loop Docker Image / build-and-publish (push) Successful in 6m42s
This commit is contained in:
@@ -0,0 +1,23 @@
|
||||
# Sub-Task 6: CraftingTab Prepare/Apply Disenchant Consolidation (Bug 8)
|
||||
|
||||
## Scope
|
||||
- **Components affected**:
|
||||
- `components/CraftingTab.tsx` (Prepare and Apply phases)
|
||||
- Item state management (add "Ready for Enchantment" tag)
|
||||
- Enchantment removal logic (disenchanting during Prepare step)
|
||||
- **Files potentially affected**:
|
||||
- `store/craftingSlice.ts` or similar for crafting state
|
||||
- `types/items.ts` (add "Ready for Enchantment" tag to item types)
|
||||
- `utils/craftingUtils.ts` (disenchant logic, tag management)
|
||||
|
||||
## Acceptance Criteria
|
||||
1. **Prepare step button text**: Shows "Start Preparation — this will remove existing enchantments" when item has existing enchantments; otherwise default text
|
||||
2. **Prepare step outcome**: After successful preparation, item receives "Ready for Enchantment" tag (verify via item state/UI)
|
||||
3. **Apply phase restriction**: Only items tagged "Ready for Enchantment" can have enchantments applied
|
||||
4. Disenchanting is fully consolidated into Prepare step (no separate disenchant UI)
|
||||
|
||||
## Dependencies
|
||||
- Sub-Task 5 (both modify CraftingTab, must run sequentially)
|
||||
|
||||
## Estimated Complexity
|
||||
- High (multi-phase UI + state management + tagging)
|
||||
Reference in New Issue
Block a user