inkdevhub
feat(revive): alternative tracing approach to debug contracts
In #143, the .debug_message field and intercept contract call feature are removed #144. We might need to implement an alternative approach to support debugging contracts with drink. See https://github.com/use-ink/ink/tree/master/integration-tests/public/debugging-strategies
Implementation suggestion: For tracing, technically we could just retrieve the call trace in related tests, and use that do similar assertions and print similar/equivalent info in tests and examples that were previously relying on TracingExtT::after_call implementations. But there's nothing Drink! specific about doing that, so may be it's kinda pointless (in the context of Drink!).
Perhaps some kind of visitor API (think tree visitor) that accepts a call trace and provides a simple API for traversing various entities in the trace would be more useful. Think associated methods like visit_call, visit_log that provide simple hooks for traversing a call trace.