CLI and Publish Tests

2026-06-02 12:12:38 -04:00
parent 7da6f554a8
commit 85834466f1
71 changed files with 511 additions and 54 deletions
@@ -0,0 +1,40 @@
+---
+type: Task
+status: Working On
+category:
+  - QA
+  - Feature
+---
+
+![[Pasted image 20260601083333.png]]
+
+- Ensure referenced data is taken from the database. Unit names and costs are currently hard coded.
+- Would be cute to dynamically change the information based on the calculator filter. i.e. when making a build for Aru, we should use the Aru unit names in the help information instead of Q'Rath
+
+
+---
+
+The TutorialHelperComponent should change it's information based on the selected Immortal and Faction.
+
+Currently, it explains a hard coded example of a user playing as Q'Rath and Orzum, and making a Legion Hall, Apostle of Bindings, a Soul Foundry, and 3 Absolvers and a Zentari.
+
+Obviously, if the the filter has Aru selected for the faction, the user would be making a Ether Maw, Altar of the Worthy, God Heart Upgrade and a Amber Womb.
+
+For the units, if they have the Immortal of Mala or Atlzan selected, they would be making Masked Hunters. But if they had Xol selected, they would instead be making Bone Stalkers.
+
+For the units, if they have the Immortal of Atlzan selected, they would be making Resinants. But if they had Mala or Xol selected, they would instead be making Blood Anchors.
+
+If they have Q'Rath selected, things are as they are. But if they have Ajari selected as the Immortal, they build Sipari instead of Zentari.
+
+The calculations should be based on the Alloy and Ether costs from the database.
+
+These variables will be need to be used, and will be taken from hard coded values on the page that matches the associated filter combinations.
+
+Given the steps can be very different between filter combinations, the exact contents will also need to be changed based on the filters. Note the extra God Heart Upgrade step for Aru.
+
+This hard coded content will need to be regenerated a a later date to match information currently in the database. But do not worry about implementing that right now.
+
+
+
+
+---