search

hyperlane-xyz / fuel-contracts

5 stars 2 forks source link

Investigate a better way of logging dispatched messages #49

Closed tkporter closed 4 months ago

tkporter commented 1 year ago

For context-- by default, using the std lib logging methods to log a struct doesn't work out of the box. See https://github.com/hyperlane-xyz/fuel-contracts/issues/3

However forc does some fancy stuff when things are logged - see the description of https://github.com/hyperlane-xyz/fuel-contracts/pull/39. Basically an ID is generated for each log call. The problem is that a lot of tooling makes use of these IDs (it's present in the contract's artifactsa and used by tooling to parse logs). It'd be nice to be able to tap into the tooling that uses these IDs

tkporter commented 1 year ago

Asking about this here https://forum.fuel.network/t/advice-around-logging-the-bytes-type/2087

nambrot commented 1 year ago

@tkporter is this still open? If so, in progress?