search

rozek / node-red-contrib-reusable-flows

a single Node-RED node representing a complete self-contained flow
MIT License
15 stars 3 forks source link

Not showing in the Node-Red Flows #1

Closed Sinevia closed 2 years ago

Sinevia commented 2 years ago

Hi @rozek

The package looks quite nice and I wanted to give it a try. But its not showing on the Node Red website which is a show stopper as it does not appear in the palette. Is there a way you can do this. If you haven't done this before the process is quite simple really, all it takes is to push it to NPM.

Also can you add release versions so that we know at what stage it is - early development, stable, etc - whether we can use with confidence :)

Many thanks

rozek commented 2 years ago

Sounds like a good idea - just give me some minutes...

rozek commented 2 years ago

actually, it has already published to npm - but that is not sufficient for being part of the list you see in Node-RED.

Let me see what I can do in order to become part of that list.

rozek commented 2 years ago

just to be complete: you may still npm install node-red-contrib-reusable-flows in the base folder of your Node-RED instance and restart Node-RED - this will make my package part of your palette

rozek commented 2 years ago

I'm currently preparing a submission through [https://flows.nodered.org/add/node]().

What is actually missing (and should be done before submission) is a help text which can be shown by the Node-RED editor - please, give me time until this evening to write that.

rozek commented 2 years ago

Oops, it was simpler than expected: the package is now part of the Node-RED library and can be found alongside the well-known "node-red-contrib-actionflows" and "node-red-contrib-components".

Thank you very much for raising this issue!

rozek commented 2 years ago

Well, I've also just made an "official release".

Please note, that (although I'm using it on a daily basis with > 100 reused flows) this package is still not "battle-hardened" yet. Using "reusable flows" after deployment should be fairly stable, but development may still cause the one or other hiccup...

Just give it a try!

Sinevia commented 2 years ago

Thank you very much @rozek. You have done a great job. Cheers.

The only thing I noticed is the releases is named as string.

I would kindly suggest following a semantic versioning as this is what most of developers are comfortable with: https://semver.org/

Its a very simple scheme vX.Y.Z - where if X is set you know the library is considered stable, and can be used in relatively "safe" manner

rozek commented 2 years ago

Done.

Thanks for the hint