Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bigstatus over-writes msg.payload #3

Open
drmibell opened this issue Jun 22, 2018 · 1 comment
Open

Bigstatus over-writes msg.payload #3

drmibell opened this issue Jun 22, 2018 · 1 comment

Comments

@drmibell
Copy link

drmibell commented Jun 22, 2018

If I understand correctly, the bigstatus node replaces msg.payload with msg.text if msg.text is defined. I don't understand the logic of this, and it makes the node much less useful to me in situations where I would like to have both msg.payload and msg.text passed through unchanged. I think that only a small change in the code would achieve this, although it could conceivably break flows that depend on the current behavior.

@Jacques44
Copy link
Owner

Hello, the node isn't an endpoint and gives informations on its outputs
You probably should connect the output of the previous node to your flow.
Perhaps you can give me more details on what you want?

Regards

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants