Skip to content

fix(logging): configure log destination and file names - #421

Open
crazy0104 wants to merge 1 commit into
ecubus:masterfrom
crazy0104:fix/log-file-destination
Open

fix(logging): configure log destination and file names#421
crazy0104 wants to merge 1 commit into
ecubus:masterfrom
crazy0104:fix/log-file-destination

Conversation

@crazy0104

Copy link
Copy Markdown
Contributor

Summary

  • change the log path browser from selecting an existing file to selecting a destination folder
  • add a separate file naming rule with field codes such as {LocalTime} and a live filename preview
  • apply the same path and naming behavior to ASC and BLF output
  • preserve existing configurations while validating Windows-safe file names and output extensions

Why

The previous browser used an open-file dialog, so users had to select an existing file even though logging creates a new file. It also did not provide a clear way to configure timestamped log names independently from the destination directory.

This change lets users select where logs should be saved and define how new log files are named before recording starts.

Validation

  • npx vitest --config vitest.config.ts run test/transport/logFile.test.ts — 5 tests passed
  • npm run typecheck
  • verified custom field-code expansion, legacy timestamp behavior, invalid-name rejection, directory preservation, and automatic extension selection

- select destination folders instead of existing files
- support field-code naming with timestamped previews
- preserve legacy paths and validate Windows-safe names
- add log naming unit tests
@crazy0104
crazy0104 marked this pull request as ready for review August 1, 2026 18:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant