12 Commits

Author	SHA1	Message	Date
wooferguy	9e3f148273	Invalid JSONata Inject node test passing condition ... This test would sometimes run twice, causing the author to increase its catch count to 2 before considering the test complete. However even one pass proves the node is behaving as expected, and it always runs at least once. I have left the conditional statement in so it can be changed in future.	2023-05-17 18:56:07 +12:00
Hiroyasu Nishiyama	7e6dfa7b92	update test for inject node	2022-05-27 12:11:53 +09:00
Hiroyasu Nishiyama	0f1aea3e0d	add test case	2022-02-15 14:41:03 +09:00
Hiroyasu Nishiyama	c948ff88a5	add support of NR_NODE_PATH	2022-01-26 21:24:48 +09:00
Hiroyasu Nishiyama	56580c4005	add test for NR_ prefix addition	2022-01-26 09:26:05 +09:00
Hiroyasu Nishiyama	983dad5b53	add test for env var access of GROUP_ID & GROUP_NAME	2022-01-25 21:07:38 +09:00
Hiroyasu Nishiyama	0ad60013aa	add test for env var access of FLOW_ID & FLOW_NAME	2022-01-25 20:52:45 +09:00
Hiroyasu Nishiyama	75bcd9e8d5	add support for accessing node id & name as env var	2022-01-14 23:40:12 +09:00
Steve-Mcl	845567d1ba	add 2 tests for user inject values	2021-05-20 22:53:32 +01:00
Nick O'Leary	717bfffa63	[Inject] Use legacy properies by preference	2020-05-11 16:07:26 +01:00
Hiroyasu Nishiyama	00e080459e	update handling of invalid jsonata expression	2020-05-11 14:51:47 +09:00
Nick O'Leary	da6db24f9e	Reorganise nodes into new categories	2019-08-21 14:23:23 +01:00