Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Added the ability to use relative time with the get-history node
- Loading branch information
Showing
4 changed files
with
215 additions
and
46 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I'd just like to leave some late feedback here as this line broke my whole setup.
Please check this field for
undefined
next time. When migrating the config after an upgrade of this node, Node Red doesn't fill it with any newly set default value but it will beundefined
at this point.So my data didn't end up in
msg.payload
but inmsg.undefined
instead, even though the Node Red GUI showed "payload" in the text field of the node's config ;)I saw that this was kept in mind in newer changes for the
get-state
node, but the upgrade path must be something I'd definitely expect to be tested from such a wide spread npm module ;) Thanks in advance :)