Stop is_intact_attr() from bubbling up messages deep in the call stack
#71
Comments
stufield
added a commit
to stufield/SomaDataIO
that referenced
this issue
Jan 5, 2024
- added new conditional logic to silence signaling messages when `is_intact_attr()` is called from within another function (indirectly) - these messages can be confusing to the user when they appear in wrapper functions, where `is_intact_attr()` is (sometimes deeply) nested - fixes SomaLogic#71
stufield
added a commit
that referenced
this issue
Jan 5, 2024
- added new conditional logic to silence signaling messages when `is_intact_attr()` is called from within another function (indirectly) - these messages can be confusing to the user when they appear in wrapper functions, where `is_intact_attr()` is (sometimes deeply) nested - fixes #71
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is an internal feature that may affect downstream users who incorporate
SomaDataIOinto their own packages.Currently
is_intact_attr()will report failed attributes calls to the console, even from deep within the call stack.This is likely unintended, the likely desired behavior is to have the console reporting only for direct calls to
is_intact_attr().The text was updated successfully, but these errors were encountered: