feat: add app name in the input placeholder

[nimish-ks]

🔍 Overview

This PR updates the DeleteAppDialog component to improve user experience by displaying the actual app name in the confirmation input field's placeholder text, rather than using a static "MyApp" placeholder. This change makes it clearer to users which app they're about to delete.

💡 Proposed Changes

• Modified the input placeholder in DeleteAppDialog to dynamically use the app name passed via props
• Removed hardcoded "MyApp" placeholder text
• Maintains all existing delete confirmation functionality and validation

🧪 Testing

• Manually tested with various app names to ensure placeholder updates correctly
• Verified that delete confirmation validation still works as expected

🎯 Reviewer Focus

Please focus on:

• DeleteAppDialog component changes (single line modification)
• Verify that the placeholder text properly updates based on the appName prop
• Confirm that delete functionality and validation remain intact

[rohan-chaturvedi]

@nimish-ks I don't think its a good idea to add the expected input field value as a placeholder. This input field gatekeeps a very destructive and irreversible action. I'd suggest instead adding the app name in the copy (eg: Please type {appName} to confirm that you want to delete this App, and use the placeholder more as a hint, something like "App name to delete", "Name of App to delete" or just "App name" .

This approach would be more in-line with the semantic purpose of an input placeholder (i.e. a brief hint): https://developer.mozilla.org/en-US/docs/Web/HTML/Attributes/placeholder

[nimish-ks]

@nimish-ks I don't think its a good idea to add the expected input field value as a placeholder. This input field gatekeeps a very destructive and irreversible action. I'd suggest instead adding the app name in the copy (eg: Please type {appName} to confirm that you want to delete this App, and use the placeholder more as a hint, something like "App name to delete", "Name of App to delete" or just "App name" .

This approach would be more in-line with the semantic purpose of an input placeholder (i.e. a brief hint): https://developer.mozilla.org/en-US/docs/Web/HTML/Attributes/placeholder

Was thinking along the same lines. Went with an empty placeholder and added app name in the copy.

thoughts?

[rohan-chaturvedi]

@nimish-ks I don't think its a good idea to add the expected input field value as a placeholder. This input field gatekeeps a very destructive and irreversible action. I'd suggest instead adding the app name in the copy (eg: Please type {appName} to confirm that you want to delete this App, and use the placeholder more as a hint, something like "App name to delete", "Name of App to delete" or just "App name" .
This approach would be more in-line with the semantic purpose of an input placeholder (i.e. a brief hint): https://developer.mozilla.org/en-US/docs/Web/HTML/Attributes/placeholder

Was thinking along the same lines. Went with an empty placeholder and added app name in the copy.

thoughts?

This works. I still think we need a placeholder, but this is enough of an improvement for now