Issues using system piping for error logging #8637
Unanswered
fallible-algebra
asked this question in
Q&A
Replies: 1 comment 1 reply
-
I agree that this would be a much more useful result. Can you reproduce it on |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I've been working on a bevy project for a couple of months and have come across a minor information hiccup with error logging.
When using system piping for error logging, the results the system return will get reported by the logging suite as coming from the wrapper system (i.e.
warn
orinfo
) rather than the function that returned the error i.e. as a stripped down version of this exampleThe latter is desired as it gives me information as to where the warning is actually coming from, and my project has a wide and deep directory tree.
I'm aware this is behaviour to be expected from using the logging suite + the system piping interfaces together, but this is suboptimal from a point of view of using system piping for error logging. Is there a macro-based approach someone else has worked on? Something that transforms a system that returns a result into a system that doesn't return a result that matches on the result in-function-body, i.e.
Or is there something else I should be relying on, have I missed something obvious, or is this all splitting hairs? Thanks.
Beta Was this translation helpful? Give feedback.
All reactions