Bug report on errors shown in node?

I am not having luck with writing code in a function node. (My fault/problem)

But what is happening seems strange.

If I am on the line, there is no error shown.
But if I move to another line, the line which I was on then shows an error:

See:

(No error visible)

I move to another line and......

Machine details:

Raspberry Pi Zero W Rev 1.1

PRETTY_NAME="Raspbian GNU/Linux 9 (stretch)"
NAME="Raspbian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"
VERSION_CODENAME=stretch
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"

Raspberry Pi reference 2017-09-07
Generated using pi-gen, https://github.com/RPi-Distro/pi-gen, 496e41575eeb9fa13f394ffb407b7bc1d00b21c2, stage5
Linux TelePi 4.19.66+ #1253 Thu Aug 15 11:37:30 BST 2019 armv6l GNU/Linux

NR 1.0.3

pi@TelePi:~/.node-red $ node -v
v10.17.0

Sorry, anything else missing?

It doesn't always show an error while you are still on the line. Is that a problem?

1 Like

Well,

If you are the local village idiot and type a line which is wrong and it doesn't show an error, I press the OK button and then I see an error for the node.

I open it and it says the line has an error.

I guess - now - you are right. (Of course you are.) It just threw me many times when I was working on that error we are discussing in the other thread.

I would type what I thought was correct and without thinking to move to another line, clicked the OK button and the node then told me there was an error.

I guess I need to move off the last line entered before pressing the OK button in future.

Sorry. Yeah. How it does it makes sense now - in retrospect.

It may be difficult for the interpreter to know that there is an error till you have finished typing. If it continually did it as you were typing it might be off-putting and also might take a lot of processor to continually re-evaluate it.

Yes, and in retrospect I totally agree.

As usual: I spoke before I thought.
(Well, maybe 90% of the time.) :wink:

A thought......

Fanciful as it is:

Granted while typing on a line you don't want error messages for that line.

But.....

If there is an error when you click the OK button, you are prompted THERE that there is an error and not after the edit screen has closed and you see the red triangle on the node and have to re-open it.

Just a thought.
Disabling the OK button - which I thought of - would not be good, as if you don't care and simply need to get out of editing that node for now..... It would be annoying.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.