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
{{ message }}
Repository navigation
Allow separate DAP log files for dart/flutter run/attach/test #5186
These settings are only used by the legacy DAP, but we could set up a logger when we spawn the debug session (and close it when the session ends) to support them here.
Actually, this doesn't make sense. The original intention of these logs was to capture the traffic going over stdin/stdout for these processes, but we no longer have it (since they're run internally in the SDK DAP).
Instead, let's add support for a new ${kind} variables in the DAP log file, which will be something like:
changed the title [-]Support the legacy log settings (flutterTestLogFile, flutterRunLogFile, dartTestLogFile, etc.) for new SDK DAPs[/-][+]Allow separate DAP log files for dart/flutter run/attach/test[/+]on Jul 16, 2024
Activity
DanTup commentedon Jul 16, 2024
Actually, this doesn't make sense. The original intention of these logs was to capture the traffic going over stdin/stdout for these processes, but we no longer have it (since they're run internally in the SDK DAP).
Instead, let's add support for a new
${kind}variables in the DAP log file, which will be something like:dart_rundart_attachdart_testflutter_runflutter_attachflutter_test[-]Support the legacy log settings (flutterTestLogFile, flutterRunLogFile, dartTestLogFile, etc.) for new SDK DAPs[/-][+]Allow separate DAP log files for dart/flutter run/attach/test[/+]