node-red / node-red/node-red-nodes
Another editor bug when checking misconfigured nodes occurs with the email node
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.1k
- Forks
- 612
- Avg merge
- 13h 57m
- Merged PRs (30d)
- 3
Description
The editor complains that node isn't configured correctly - but it works well.
I had a similar problem after NodeRed Version 3.1.1. with the switch node.
Current version of NodeRed - with this error: 3.1.3
Current verson of the email node is: 2.1.0
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the editor warning with Node-RED 3.1.3 and email node 2.1.0, comparing the node's configured behavior with the editor's validation result. Trace the email node's editor entry point and configuration checks. Done means a working email node is no longer reported as misconfigured, with the regression covered by an appropriate test if one exists.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100