fix: input node field name

[JeanKaddour]

This pull request includes a change to the baseNodeComparator function in the BaseNode.tsx file to improve the comparison logic for node components. The most important change is the addition of a deep comparison for the children property using the isEqual function.

• frontend/src/components/nodes/BaseNode.tsx: Modified the baseNodeComparator function to include a deep comparison of the children property to ensure that changes in nested components are properly detected.

---

Important

Add deep comparison for children in baseNodeComparator in BaseNode.tsx to detect nested component changes.

• Behavior:
  • Modified baseNodeComparator in BaseNode.tsx to include deep comparison of children property using isEqual to detect changes in nested components.

^{This description was created by for 3f3e542. It will automatically update as commits are pushed.}

[ellipsis-dev]

👍 Looks good to me! Reviewed everything up to 3f3e542 in 55 seconds

More details

• Looked at 14 lines of code in 1 files
• Skipped 0 files when reviewing.
• Skipped posting 2 drafted comments based on config settings.

1. frontend/src/components/nodes/BaseNode.tsx:115

• Draft comment:
  Using lodash isEqual for deep comparing children can be costly. Consider verifying if a shallow comparison (or normalizing children) suffices for performance, especially with large or complex nodes.
• Reason this comment was not posted:
  Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 20% vs. threshold = 50%
  The comment raises a valid performance concern - deep comparison can be expensive with complex nested structures. However, React children are typically not deeply nested objects but rather React elements which can be compared more simply. The comment suggests alternatives like shallow comparison or normalization but doesn't provide concrete guidance. The performance impact would depend heavily on the actual structure of children being passed.
  I may be underestimating the performance impact - if children contain large nested data structures, the deep comparison could cause noticeable slowdowns. However, I may also be overvaluing a premature optimization.
  While the performance concern is theoretically valid, without evidence of actual performance problems in production, this feels like premature optimization. React children are usually not deeply nested data structures.
  The comment should be deleted as it suggests optimization without clear evidence of performance problems, and doesn't provide specific actionable guidance.

2. frontend/src/components/nodes/BaseNode.tsx:116

• Draft comment:
  Using lodash's isEqual for deep comparison of children can be expensive if the children structure is large or frequently changing. Confirm that children are stable and that the performance impact is acceptable.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50%
  None

Workflow ID: wflow_LSZAPKUcbu8EeUxh

---

You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.