feat: add delete functionality for text and list steps

[RohitR311]

After Capture Text and Capture List data fields confirmation provide the option to delete the field.

Summary by CodeRabbit

• New Features

  • Added ability to delete confirmed text steps and list text fields directly from the user interface.
  • Introduced delete buttons for confirmed entries to improve user interaction and content management.
  • Added "delete" button in multiple language localizations (German, English, Spanish, Japanese, Chinese) for consistent user experience.

• User Experience

  • Enhanced component functionality to allow more flexible editing of text and list fields.

[coderabbitai]

Walkthrough

The pull request introduces deletion functionality for text steps and list text fields within the RightSidePanel component. Two new methods, handleTextStepDelete and handleListTextFieldDelete, are implemented to allow users to remove confirmed text steps and list text fields from the UI. The changes modify the rendering logic to include delete buttons for confirmed entries, enabling more flexible management of text and list fields. Additionally, localization files are updated to include a "delete" button in multiple languages.

Changes

File	Change Summary
src/components/organisms/RightSidePanel.tsx	- Added handleStartGetText() method - Added handleStartGetList() method - Added handleTextStepDelete(id: number) method for deleting confirmed text steps - Added handleListTextFieldDelete(listId: number, fieldKey: string) method for deleting list text fields - Added state variables: isCaptureTextConfirmed and isCaptureListConfirmed - Modified rendering logic to conditionally include delete buttons for confirmed entries
public/locales/de.json	- Added "delete": "Löschen" under right_panel.buttons section
public/locales/en.json	- Added "delete": "Delete" under right_panel.buttons section
public/locales/es.json	- Added "delete": "Eliminar" under right_panel.buttons section
public/locales/ja.json	- Added "delete": "削除" under right_panel.buttons section
public/locales/zh.json	- Added "delete": "删除" under right_panel.buttons section

Possibly related PRs

• fix: preserve previous labels steps before adding list step #288: Involves handling of labels in list steps, which is related to the confirmation and deletion functionalities introduced in the main PR for the RightSidePanel component, as both involve managing user interactions with text and list fields.

Suggested reviewers

• amhsirak

Poem

🐰 Hop, hop, delete with glee!
Text steps vanish, fields set free
Buttons clicked with rabbit might
Cleaning up the UI so bright
CodeRabbit's magic, clean and neat! 🗑️

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 3cf0b85 and 0ba0839.

📒 Files selected for processing (1)

• src/components/organisms/RightSidePanel.tsx (12 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• src/components/organisms/RightSidePanel.tsx

---

🪧 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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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. (Beta)
• @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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (3)

src/components/organisms/RightSidePanel.tsx (3)

172-186: Consider consolidating delete and discard logic for text steps.

The new handleTextStepDelete method closely mirrors the logic in handleTextStepDiscard, both removing the text step from state. Although the operations differ slightly in intent (discarding unconfirmed vs. deleting confirmed), you could unify parts of their internal logic to reduce duplication, or explore whether they can share utility functions.

---

561-575: Provide a user confirmation dialog before irreversible deletion.

The user experience could benefit from a brief confirmation step (e.g., a modal) before deleting a confirmed text step. Although the code cleanly handles “delete,” a confirmation would reduce the risk of accidental data loss.

---

Line range hint 623-649: Similarly, prompt users before deleting confirmed list fields.

As with text steps, consider adding a confirmation dialog when deleting confirmed list fields in handleListTextFieldDelete, to ensure that users do not accidentally remove valuable data.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 4b12139 and 6ac3e19.

📒 Files selected for processing (1)

• src/components/organisms/RightSidePanel.tsx (5 hunks)

🔇 Additional comments (1)

src/components/organisms/RightSidePanel.tsx (1)

214-229: Maintain consistency and guard against potential key mismatches.

The handleListTextFieldDelete method properly removes the relevant field from confirmedListTextFields and errors. One possible enhancement is to log or handle situations where the fieldKey might not exist in the list, ensuring consistency if the database or upstream code has changed.

[amhsirak]

@RohitR311 A passing thought : should we allow to delete steps after "confirm capture" - for both capture text and capture list.