Timmiej93

Results 6 comments of Timmiej93

I don't know man, this example says otherwise: ``` [{"id":"c69ade348cbac61c","type":"subflow","name":"Subflow 1","info":"","in":[{"x":60,"y":80,"wires":[{"id":"b6e92770238482d4"}]}],"out":[]},{"id":"b6e92770238482d4","type":"debug","z":"c69ade348cbac61c","name":"","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"false","statusVal":"","statusType":"auto","x":200,"y":80,"wires":[]},{"id":"0892087d430bef41","type":"inject","z":"4d177dfea3653f94","name":"","props":[{"p":"payload"},{"p":"topic","vt":"str"}],"repeat":"","crontab":"","once":false,"onceDelay":0.1,"topic":"","payload":"","payloadType":"date","x":310,"y":260,"wires":[["436fb36c116fb4ab"]]},{"id":"436fb36c116fb4ab","type":"subflow:c69ade348cbac61c","z":"4d177dfea3653f94","name":"","x":580,"y":260,"wires":[]}] ``` I know you can't enable/disable debug outputs inside subflows (god only knows why...), but they sure seem to...

Personally, coming from regular coding, that doesn't make sense to me. I view a subflow as a function in regular code. Write once, use many times. In a regular function...

I have found a much easier way to get around this issue, for most cases. Write your large script and store it on dropbox. On dropbox, copy the "dropbox link"....

> It defeats the purpose of Diun which sends notifications when an image update is available. I don't see how adding the option to also send a notification for images...

So I'm guessing that all 5 statuses [here](https://github.com/crazy-max/diun/blob/2c3619225798a3a18d196c4b6a40c82515283a3e/internal/model/image.go#L27) are accepted arguments for `diun.notify_on` [here](https://crazymax.dev/diun/providers/docker/#docker-labels)? If so, this feature request would turn into a bug report for the documentation ;). It...

So the states exist, they're just not functional? If so, why do the other states exist, especially since you mentioned you don't agree with adding `unchange` (which I don't quite...