[Bug] Во вкладке управления - команды нет кнопок действия на действия команд кодом

[mmeerrkkaa]

Во вкладке управления - команды нет кнопок действия на действия с кодом

Тип изменился на code. У нас была старая версия для типа, просто слегка поменять

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

✅ Successfully generated implementation plan.

💡 Use @coderabbitai <feedback> to replan

Examples

• Example 1
• Example 2

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[coderabbitai]

Warning

A plan generation is already in progress. Please wait for it to complete before requesting a new plan.

[coderabbitai]

Coding Plan

Approach

Ticket Summary

Action buttons are not appearing in the management tab for Code-type commands. The type system changed to use "code" as a designation, and the UI conditional logic needs to be updated to show appropriate action buttons for Code commands alongside Visual commands.

Observations

Codebase Summary

BlockMine is a React + Node.js web application for managing Minecraft bots. The command management interface is located in frontend/src/components/management/CommandsManager.jsx, which displays a table of commands with type-based badges and action buttons. Commands are distinguished as either Visual (with isVisual flag or graphJson present) or Code (all others). Currently, the UI only renders action buttons for Visual commands, leaving Code commands with just a dash placeholder.

Assumptions

Assumption 1: Which action buttons should Code commands display?

Options Considered:

• Show identical buttons for both types (not logical, Code commands can't open in visual editor)
• Show Edit and Delete buttons for Code commands (aligns with existing modal flow)
• Show only Delete button for Code commands (insufficient functionality)

Chosen Option: Show Edit and Delete buttons for Code commands (aligns with existing modal flow)

Rationale: The Edit button opens the existing CommandDetailDialog (which already works when clicking the row), providing a dedicated button for this action. This approach reuses existing dialog functionality and provides parity in command management capabilities across both types.

💡 User Tips

Regenerate the plan with different choices with @coderabbitai <feedback>.

Implementation Steps

Update Action Button Rendering Logic

Update the command table's action button column to display appropriate buttons for both Visual and Code commands, replacing the current dash placeholder for Code commands.

Task 1: Modify Action Button Conditional Rendering

Update the button rendering logic in CommandsManager.jsx to show action buttons for all commands instead of only Visual commands.

• Replace the current conditional (command.isVisual || (command.graphJson && command.graphJson !== 'null')) that gates all button rendering
• Implement two separate button sets: one for Visual commands (Open, Export, Delete) and one for Code commands (Edit, Delete)
• For Visual commands: retain existing Open, Export, and Delete buttons with current behavior
• For Code commands: add Edit button that opens CommandDetailDialog and Delete button with confirmation

Task 2: Wire Edit Button Handler for Code Commands

Connect the Edit button for Code commands to the existing modal opening logic.

• Reuse the existing handleOpenModal function that sets editingCommand state and opens isModalOpen
• Ensure the Edit button triggers the same flow as clicking the table row for Code commands
• Maintain current navigation behavior for Visual commands (routing to visual editor)
• Apply consistent styling between Edit button for Code commands and Open button for Visual commands for visual parity

🤖 Prompt for AI agents

Update CommandsManager.jsx to display action buttons for both Visual and Code
commands.

Remove the conditional check that only renders buttons for Visual commands.
Implement type-based button rendering:
- For Visual commands: show Open, Export, and Delete buttons (preserve existing
behavior)
- For Code commands: show Edit and Delete buttons

For Code commands Edit button:
- Call existing `handleOpenModal` function to open CommandDetailDialog
- Apply similar styling as the Open button for consistency

Ensure Delete button works for both command types with confirmation flow.

---

🚀 Next Steps

🤖 All AI agent prompts combined

Update CommandsManager.jsx to display action buttons for both Visual and Code
commands.

Remove the conditional check that only renders buttons for Visual commands.
Implement type-based button rendering:
- For Visual commands: show Open, Export, and Delete buttons (preserve existing
behavior)
- For Code commands: show Edit and Delete buttons

For Code commands Edit button:
- Call existing `handleOpenModal` function to open CommandDetailDialog
- Apply similar styling as the Open button for consistency

Ensure Delete button works for both command types with confirmation flow.

💡 Iterate on the plan with: @coderabbitai <feedback>

Example Feedback
- @coderabbitai You can skip phase 3. Add a simple unit test case for phase 2.
- @coderabbitai For assumption 1 go ahead with option 3 and replan.

---

💬 Have feedback or questions? Drop into our discord!