node-red / node-red/node-red-nodes
Node-red-node-email (get) not dedected by Complete node
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.1k
- Forks
- 612
- Avg merge
- 13h 57m
- Merged PRs (30d)
- 3
Description
node-red-node-email 1.7.4
Node-RED v1.0.2
Hi, Node-RED team!
I have discovered that the node-red-node-email (email in) does not provide the complete status according to (https://nodered.org/blog/2019/09/20/node-done)
It would be helpful to have the complete status available.
Even if the email in node has two options on how to start (automatic and triggered), it would be helpful in both cases to know when the node has completed its action.
IMO, the information could be:
- node triggered (either automatically every x seconds or manually)
- connect()
- fetch()
if (email exists) deliver_content()
- done()
Thanks!
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 locating the node-red-node-email email in implementation and trace its automatic and triggered flows. Compare both paths with Node-RED's complete status guidance in the linked blog post; done means the node reports completion after fetching and delivering available email content in each mode.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100