[knolleary]

Node-RED project lead here :wave:

That's all useful feedback to us. There's always a balance to be had between putting lots of code in Function nodes and the visual complexity of doing the equivalent in pure nodes. Part of that is understanding where users are falling back to JS in a Function node - and what could the core nodes provide to avoid that necessity.

Code reviews are a common piece of feedback and something we need to help with.

In the day job (FlowFuse CTO) we're looking at how to improve the overall developer UX of Node-RED - both within node-red, but also how you manage it within a team and at scale.

If you had any more feedback on your experiences, would love to hear it.

[daniel-payne]

the issue of code reviews is a problem in standard node-red, the flows.json does not lend its self to git management. I wrote an integration between node-red and vs-code, it's in the node-red forum and the comment bellow.

It fixes this problem, and also fixes a problem of integrating with test tools and code coverage tools.

It's the old 80/20 rule, 80% can be done very quickly with easy to configure out of the box nodes, but it's the last 20% of functionality that takes all the time.

Dropping out to vs-code for this 20% improved my productivity a lot.

TBH I don't know how I would do a code review with n8n, i will need to do more investigation.