You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: NEWS.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,11 +2,11 @@
2
2
3
3
#### New Features
4
4
5
-
* Aio fields`$result` for a 'sendAio', `$raw`and`$data`for a 'recvAio' may be queried directly, returning their values or else an NA 'unresolved value' if the Aio operation is yet to complete.
6
-
*`unresolved()` added as an auxiliary function to query whether an Aio is still unresolvedin a non-blocking fashion.
5
+
* Aio values`$result`, `$raw`or`$data`now resolve without requiring `call_aio()`. Access the values directly and an NA 'unresolved value' will be returned if the Aio operation is yet to complete.
6
+
*`unresolved()` added as an auxiliary function to query whether an Aio is unresolved, for use in control flow statements.
7
7
*`is_nul_byte()` added as a helper function for request/reply setups.
8
8
*`survey_time()` added as a convenience function for surveyor/respondent patterns.
9
-
*`logging()` function to specify a global package logging level - currently supports 'error' and 'info'.
9
+
*`logging()` function to specify a global package logging level - 'error' or 'info'. Automatically polls the environment variable 'NANONEXT_LOG' on package load and then each time `logging(level = "check")` is called, allowing this to be set externally.
10
10
*`ncurl()` adds a '...' argument. Support for HTTP methods other than GET.
Copy file name to clipboardExpand all lines: README.Rmd
+4-1Lines changed: 4 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -277,9 +277,12 @@ In such a case, using `call_aio()` confirms that the operation has completed (or
277
277
278
278
{nanonext} fully implements NNG's pub/sub protocol as per the below example.
279
279
280
-
This example uses the new R4.1 pipe for clarity of code, although this is of course not required.
280
+
The built-in logging levels are also demonstrated here. NNG errors are always output to stderr and operation is otherwise silent by default. To enable key information events to be sent to stdout, use `logging(level = "info")`.
281
+
282
+
The log level can also be set externally in production environments via an environment variable `NANONEXT_LOG`.
0 commit comments