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
Currently, a lot of messaging in with_nix() is controlled by helper functions and mainly by the message_type argument. Usually these are printed or not at the appropriate computation steps. Another option would be to collect all messages at a certain log level and print a selection of relevant steps to the console at the end of the with_nix() call. This might give better fine-grained control over messaging, but we will have to see if the slight extra complexity is worth it.
Future idea: maybe there is a way to make a report so that we first collect all log levels for whatever option (verbose,...), serialise that, and serialise and maybe filter that into the current R session.
cc @b-rodrigues what we discussed at the Luxembourg meeting last week :-) just keep it as a track record issue. We can close it later if we think it is unnecessary.
The text was updated successfully, but these errors were encountered:
philipp-baumann
changed the title
with_nix(): [future- id]with_nix(): [future idea] maybe collect the log levels
Jun 15, 2024
Currently, a lot of messaging in
with_nix()
is controlled by helper functions and mainly by themessage_type
argument. Usually these are printed or not at the appropriate computation steps. Another option would be to collect all messages at a certain log level and print a selection of relevant steps to the console at the end of thewith_nix()
call. This might give better fine-grained control over messaging, but we will have to see if the slight extra complexity is worth it.cc @b-rodrigues what we discussed at the Luxembourg meeting last week :-) just keep it as a track record issue. We can close it later if we think it is unnecessary.
The text was updated successfully, but these errors were encountered: