Skip to content

Unexpected missing catch node #48

@FStefanni

Description

@FStefanni

Hi,

working on tests for a node of mine, I have discovered that I must explicitly load the catch node, with something like:

const catchNode = require("../../node_modules/@node-red/nodes/core/common/25-catch");
helper.load([catchNode, ...], ...);

This is quite unexpected, since "standard nodes" are supposed to be already available.
But, even worse, we have to manually load a file, which is a node-red internal file.
IMHO users should not even know about its existence: since it is a single internal file,
it could be deleted/moved/renamed/etc., breaking third-party tests.
So this seems to create a serious usability issue for node-red-node-test-helper by third-party tests.

The question:

Is this truly needed or am I missing something? Or maybe there is a better way? And what is your point of view on this usability issue?

Regards.

EDIT/PS

I have not checked other standard nodes, but the same considerations could apply also to them, if the same loading procedure is required

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions