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 seems to (generally) output correctly for module-level functions, but breaks with class-level.
Before closing issue, should also examine functions in nested classes, as well as outputting a default value in event of future call-stack examination issues.
The text was updated successfully, but these errors were encountered:
Currently works when dumping a function and a function on an object. But fails to find the function name if the function is deeper within an object. EX: dump(obj_a.prop_b.do_work) will not be able to find the name of do_work. But, should we really be dumping things in this manner anyway? It seems more likely to just dump obj_a and then inspect.
Was determined that they should be functionality that is included. Should be fully fixed as there is an entirely new way of getting the dumped variable's name that is way simpler and handles making nested calls inside the dump.
Seems to be related to call-stack examination.
Currently seems to (generally) output correctly for module-level functions, but breaks with class-level.
Before closing issue, should also examine functions in nested classes, as well as outputting a default value in event of future call-stack examination issues.
The text was updated successfully, but these errors were encountered: