Removed theme runner selection step from the installer.

[AlexSkrypnyk]

Summary by CodeRabbit

• Refactor

  • Removed the prompt and related options for selecting a theme asset build tool during installation.
  • Updated labels and emojis for improved clarity and consistency in provisioning prompts.

• Tests

  • Removed tests and coverage related to the theme asset build tool prompt.

[coderabbitai]

Walkthrough

The changes remove the ThemeRunner class and all related references throughout the codebase, including its prompt, handler logic, and associated test scaffolding. This affects the prompt management, functional and unit tests, and eliminates the unused or placeholder theme asset compilation feature.

Changes

Files/Groups	Change Summary
.vortex/installer/src/Prompts/Handlers/ThemeRunner.php	Deleted the ThemeRunner class, its constants, and unimplemented methods.
.vortex/installer/src/Prompts/PromptManager.php	Removed all references to ThemeRunner, including prompt, handler logic, imports, and prompt labels updated for emoji consistency.
.vortex/installer/tests/Functional/InstallTest.php	Deleted import and PHPUnit coverage annotation for ThemeRunner.
.vortex/installer/tests/Unit/PromptManagerTest.php	Removed all references, imports, and test data for ThemeRunner from the unit test file.

Poem

A runner for themes, now gone from the scene,
No more Grunt or Gulp in our install routine.
The prompts are now lighter, the tests are more lean,
With code freshly swept, our project stays clean.
🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 98a4207 and dfc81ff.

📒 Files selected for processing (1)

• .vortex/installer/src/Prompts/PromptManager.php (10 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (13)

• GitHub Check: build (1)
• GitHub Check: build (0)
• GitHub Check: vortex-test-common
• GitHub Check: vortex-test-deployment (1)
• GitHub Check: vortex-test-workflow (1)
• GitHub Check: vortex-test-deployment (0)
• GitHub Check: vortex-test-workflow (2)
• GitHub Check: vortex-test-workflow (3)
• GitHub Check: vortex-test-workflow (0)
• GitHub Check: vortex-test-installer (8.4)
• GitHub Check: vortex-test-installer (8.2)
• GitHub Check: vortex-test-installer (8.3)
• GitHub Check: vortex-test-docs

🔇 Additional comments (10)

.vortex/installer/src/Prompts/PromptManager.php (10)

117-117: Good emoji consistency improvement.

Replacing "🔖" with "🏷️" provides better visual consistency for label-related prompts.

---

127-127: Consistent emoji update.

Good continuation of the emoji standardization using "🏷️" for name/label prompts.

---

205-205: Appropriate emoji choice for GitHub project name.

Using "🏷️" maintains consistency with other name/identifier prompts.

---

231-231: Better semantic emoji for profile prompt.

Using "🧾" for profile is more semantically appropriate than the generic "🔖" tag emoji.

---

349-349: Improved terminology precision.

"Assembled codebase" is more precise than "built codebase" in the context of provisioning, as it better describes the state where dependencies and assets are gathered but not necessarily compiled.

---

352-352: Thematically appropriate emoji choice.

The butterfly emoji "🦋" for provision type suggests transformation/metamorphosis, which aligns well with the provisioning process concept.

---

384-384: Improved label clarity and appropriate emoji.

Changing from "Database dump source" to "Database source" is more concise, and the satellite emoji "📡" effectively represents data source/transmission.

---

398-398: Consistent emoji usage for container image prompt.

Using "🏷️" maintains the established pattern for identification/naming prompts.

---

577-611: Summary labels updated for consistency.

The emoji changes in the summary output maintain consistency with the prompt labels, ensuring a cohesive user experience.

---

584-628: Consistent emoji updates throughout summary.

All the emoji changes align with the corresponding prompt updates, maintaining visual consistency between the prompts and the final summary display.

✨ Finishing Touches

• 📝 Generate Docstrings

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 71.70%. Comparing base (2c70915) to head (dfc81ff).
Report is 2 commits behind head on develop.

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #1723      +/-   ##
===========================================
- Coverage    71.81%   71.70%   -0.11%     
===========================================
  Files           78       77       -1     
  Lines         4403     4386      -17     
===========================================
- Hits          3162     3145      -17     
  Misses        1241     1241              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.