72 lines
2.9 KiB
Plaintext
72 lines
2.9 KiB
Plaintext
# Node-RED Dashboard Stop Prompt Issue - Systematic Debugging
|
|
|
|
## PROJECT CONTEXT
|
|
I'm working on a Node-RED dashboard with start/stop cycle counting functionality. I need to fix critical issues with the stop prompt dialog before adding graphs and alerts today.
|
|
|
|
## CURRENT PROBLEM
|
|
The stop prompt dialog has multiple failures:
|
|
1. Stop prompt appears INSIDE the scrap prompt (incorrect nesting/placement)
|
|
2. Stop button is non-functional
|
|
3. Submit and Cancel buttons in stop prompt are unclickable
|
|
4. The dialog should ask "why are you stopping?" in a themed, two-column layout that fits on screen without zooming
|
|
|
|
## WHAT WORKED BEFORE
|
|
I had a working scrap prompt implementation with the same logic that I'm trying to replicate for the stop prompt.
|
|
|
|
## WHAT I NEED FROM YOU
|
|
|
|
### Phase 1: Analysis
|
|
1. Review ALL relevant code files (HTML, JavaScript, Node-RED flows, CSS)
|
|
2. Identify the working scrap prompt implementation as reference
|
|
3. Map out where the stop prompt code is currently located
|
|
4. Identify specific issues:
|
|
- Why is nesting occurring?
|
|
- What's breaking the button functionality?
|
|
- What's preventing Submit/Cancel interaction?
|
|
|
|
### Phase 2: Solution Planning
|
|
1. Create a clear fix strategy that:
|
|
- Preserves the working scrap prompt
|
|
- Implements stop prompt as a separate, parallel dialog
|
|
- Maintains dashboard theme consistency
|
|
- Ensures two-column layout for compact display
|
|
2. Identify any dependencies or conflicts between components
|
|
3. Plan changes in order of execution to avoid breaking working features
|
|
|
|
### Phase 3: Phased Implementation
|
|
Break the fix into small, testable steps:
|
|
- Each phase should be independently verifiable
|
|
- No phase should break existing functionality
|
|
- Clear success criteria for each phase
|
|
|
|
## CRITICAL REQUIREMENTS
|
|
- ✅ Stop prompt must be SEPARATE from scrap prompt
|
|
- ✅ Both dialogs must function independently
|
|
- ✅ All buttons (Start, Stop, Submit, Cancel) must work
|
|
- ✅ Two-column layout for stop reasons
|
|
- ✅ Theme-consistent styling
|
|
- ✅ No zoom required to view dialog
|
|
- ✅ Preserve all existing working functionality
|
|
|
|
## DELIVERABLES NEEDED
|
|
1. Root cause analysis with specific line/section references
|
|
2. Step-by-step fix plan with rationale
|
|
3. Phased implementation approach (3-5 phases max)
|
|
4. Code changes for each phase with clear before/after
|
|
5. Testing checklist for each phase
|
|
|
|
## PROJECT FILES TO EXAMINE
|
|
Please start by asking me to share:
|
|
- Node-RED dashboard HTML/template nodes
|
|
- JavaScript functions handling start/stop
|
|
- CSS styling files
|
|
- Flow configuration for the stop/scrap logic
|
|
- Any custom UI nodes or templates
|
|
|
|
## CONSTRAINTS
|
|
- Must complete today alongside adding graphs and alerts
|
|
- Cannot break working scrap prompt functionality
|
|
- Must maintain current dashboard theme/styling
|
|
- Solution must be production-ready, not a prototype
|
|
|
|
Please begin by requesting the relevant code files, then provide your analysis following the phase structure above. |