Skip to content

Workspace name/folder as macro for log #5154

@FMorschel

Description

@FMorschel

Is your feature request related to a problem? Please describe.
I received instructions to set the extension to save log files. E.g.:

"dart.flutterRunLogFile": "C:\\Dev\\Logs\\flutter_run.txt",
"dart.vmServiceLogFile": "C:\\Dev\\Logs\\vm_service.txt",
"dart.dapLogFile": "C:\\Dev\\Logs\\dap.txt",

When looking for these in VSCode settings, I found out about ${name} being supported inside the path as a macro for the debug session name.

However, I was also instructed to set these settings for each workspace so that different workspaces don't conflict with each other. Which is a little too verbose when having lots of projects that you'd like to log.

Describe the solution you'd like
I'd like for the extension to support ${folder} or ${workspace} or similar so that I can create a path like ~/dev/logs/${workspace}/${name}.

Describe alternatives you've considered
Manually creating an inner folder for each workspace and defining it to the workspace settings.

Additional context
I was also reminded that some workspaces in VSCode can be unnamed. So in this case I believe the files could be simply left under ~/dev/logs/${name} as for my example.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions