88 lines
2.1 KiB
Plaintext
88 lines
2.1 KiB
Plaintext
IMPORTANT — READ BEFORE FIXING ANYTHING:
|
|
|
|
When you propose a fix, you MUST check for side effects.
|
|
|
|
I am working on a Node-RED workflow where several nodes depend on each other. Recently, when one thing is fixed, another unrelated part stops working. I want you to STOP doing patch-fixes and instead analyze the ENTIRE LOGIC FLOW end-to-end before proposing code.
|
|
|
|
You MUST follow these rules:
|
|
|
|
1. Holistic Analysis
|
|
|
|
Before giving any solution, analyze:
|
|
|
|
how the fix affects upstream nodes
|
|
|
|
how it affects downstream nodes
|
|
|
|
dependencies between function nodes
|
|
|
|
whether msg.topic, msg.payload, globals, or context variables may break other logic
|
|
|
|
how this impacts UI behavior (button disabling, enabling, validation)
|
|
|
|
2. Backwards Compatibility
|
|
|
|
Any fix you propose MUST keep ALL previous working behaviors intact, including:
|
|
|
|
start/stop workflow
|
|
|
|
UI button states
|
|
|
|
preset loading logic
|
|
|
|
database queries
|
|
|
|
error handling
|
|
|
|
If a fix breaks even ONE thing that was previously working, you must rethink and propose an alternative.
|
|
|
|
3. Side-Effect Detection
|
|
|
|
For EVERY change you suggest, explicitly list:
|
|
|
|
what might break
|
|
|
|
why it might break
|
|
|
|
how to prevent that
|
|
|
|
whether I must update other nodes
|
|
|
|
If something is unclear, ASK ME before giving a fix.
|
|
|
|
4. Validate the Entire Flow
|
|
|
|
After proposing a solution, simulate in your reasoning:
|
|
|
|
what happens when I press Start
|
|
|
|
when I press Stop
|
|
|
|
when work order + mold are selected
|
|
|
|
how messages propagate across nodes
|
|
|
|
how context variables change
|
|
|
|
If a solution does not work in all these scenarios, do not propose it.
|
|
|
|
5. Output Format
|
|
|
|
Your answer MUST follow this structure:
|
|
|
|
Root Cause Analysis
|
|
|
|
Full-Flow Simulation (explain what happens from beginning to end)
|
|
|
|
Proposed Fix
|
|
|
|
Impact Check (exactly what stays unaffected)
|
|
|
|
Side-Effect Prevention
|
|
|
|
Clear final code snippet
|
|
|
|
If you cannot guarantee that your solution does NOT break other parts, ask questions before generating any code.
|
|
|
|
|
|
Right now what is going on is that the start button stays grayed out, Im sure that the stop prompt works, but Im not being able to see it because iven though I select Wo and mold, I cant click start button due to it being gray. |