mirror of
https://github.com/flutter/flutter.git
synced 2026-02-20 02:29:02 +08:00
4c46030927
From https://github.com/flutter/flutter/issues/143348#issuecomment-2016047148: > before we ship, we should add a printTrace to the tool about each asset transformer we're invoking and the path/arguments we called it with I think this is a good idea since asset transformers can be arbitrary Dart programsâmeaning that a lot can go wrong when running them. For example, they can hang indefinitely or perform some sort of I/O that later results in a tool crash. Knowing that asset transformation was involved when debugging a crash (or a slow/stuck `flutter build`) could be useful, so I think adding a `printTrace` or two is a good idea (or at least not a bad one).