Oh I have it again (the behavior) but I don't know how
Mmm, it seems that not all nodes trigger nrlint - If I make an error in the debug node (ends with dot), the node doesn't have the "!"
Oh I have it again (the behavior) but I don't know how
Mmm, it seems that not all nodes trigger nrlint - If I make an error in the debug node (ends with dot), the node doesn't have the "!"
@knolleary Sorry to bother you again. Could you please take a look at this?
It’s schools half term break here. I think Nick is on vacation this week.
A few hours of debugging later:
This code line in a function node
msg.payload = msg.payload +'\r';
causes nrlint to be trapped in an endless loop (or eslint to be more precise)!
I think this is Node red tab hogging the processor in the browser · Issue #36 · node-red/nrlint · GitHub
@knolleary, when you are back, I see that you closed that issue some time ago. Does that mean we should no longer see it?
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
@knolleary are you able to comment on this?
Looks like we merged the fix but never published it. Will got a new version published today.
Great, thanks.
Thank you very much! It´s working now.