Closed OrlandodaSilva closed 3 years ago
Hi, This has already been reported on the Node-RED forum. But got no feedback on that yet. I assume it is a bug of the site... Bart
Can you put the code for "Set text content via msg" in the wiki here so we can still copy and see how you do things while you wait for feedback from the Node Red forum. I am interesting how you did this. Thanks !
@OrlandodaSilva, Last week Nick reported that the length of the readme page should be limited, because the NPM API (which he calls to copy the readme to flows.nodered.org) truncates the pages at some length. So only thing I can do is to split my readme page into multiple pages...
@tttdevelop, Until I have split the readme page for NPM, you can always see the full readme page here in this Github repository. Or did I misinterpret your question perhaps?
@bartbutenaers - Nope. Your answer is perfect. Didn't think about looking at the README.MD. I was looking at your wiki.
I have split the readme page on Github into multiple files. Hopefully it will become now more readable on npm and flows.nodered.org. This change will be published on npm very soon, as part of the 2.2.0 release.
Version 2.2.0 has been published on NPM, which contains a smaller readme page (with links to other pages).
Hi, I have been using your documentation on https://flows.nodered.org/node/node-red-contrib-ui-svg/in/590bc13ff3a5f005c7d2189bbb563976 If you scroll to the very bottom you will notice that the document appears to be corrupt. Is it possible to have it corrected or is it outside your scope.