Skip to content

Conversation

fusmanii
Copy link
Contributor

With across-protocol/sdk#1169 .toNative() for addresses in logger is redundant

@grasphoper
Copy link
Contributor

grasphoper commented Aug 21, 2025

@fusmanii have you confirmed that this is the case? (That the .toNative() is not required) I remember hitting some instances of full JSON object properties logging for Address sometimes

@pxrl
Copy link
Collaborator

pxrl commented Aug 22, 2025

@fusmanii have you confirmed that this is the case? (That the .toNative() is not required) I remember hitting some instances of full JSON object properties logging for Address sometimes

I've also noticed this - we currently have an issue with an error message dumping the full Address class. I'm not 100% sure, but I think it might be an issue when an Address class is supplied directly as a logging argument, vs. when it's bundled inside another object. Needs further investigation to confirm.

@fusmanii fusmanii added the do not merge Don't merge until label is removed label Aug 22, 2025
@fusmanii fusmanii force-pushed the faisal/remove-tonative-from-logs branch from a4324db to 93b4d05 Compare August 22, 2025 13:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
do not merge Don't merge until label is removed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants