ahochsteger / gmail-processor / 24288091688

96%

Build Type

push

github

Committed by web-flow

Commit Message

feat: add file conflict strategy `increment` (#652)

feat(adapter): add `increment` conflict strategy for Google Drive files

Closes #633

When creating a file in Google Drive and a naming conflict occurs, the
new `increment` conflict strategy automatically appends a counter suffix
(e.g. ` (1)`) to the filename, incrementing until a free name is found.
The suffix format is fully customizable via three new `StoreActionBaseArgs`
parameters:
- `incrementStart` (default: `1`)
- `incrementPrefix` (default: `" ("`)
- `incrementSuffix` (default: `")"`)

This allows matching Windows-style naming (`file (1).txt`) or custom
conventions (`file_2.txt`).

Additional changes included in this PR:

- feat(e2e): add `E2EAssertionHelper` with fluent methods (`findAction`,
  `expectActionExecuted`, `expectActionMeta`, `expectActionOrder`) to
  drastically reduce E2E test verbosity; harden key lookups with
  mandatory `arg.`/`meta.` prefixes; add native `RegExp` and lazy
  function evaluation support to `E2E.expect`
- feat(e2e): introduce `E2EDefaults.driveTestBasePath()` for structured,
  date-scoped and run-isolated Drive paths across all examples
- refactor(env): consolidate environment initialization; merge
  `runMode`, `CacheService`, and `PropertiesService` into `envOverrides`
  in `EnvProvider.defaultContext`; simplify `run()` and all E2E
  templates accordingly
- refactor(env): fix metadata passing in `customActionsAdvanced` by
  setting the extraction action to `PRE_MAIN` processing stage; use
  literal `actionMeta` objects for GAS compatibility
- test: harden unit test coverage and fix cross-test interference
  (spy leakage, shared object mutation, orphaned `test.todo` cleanup,
  coverage tooling consolidation into `jest.config.js`, removal of
  deprecated `sonar.typescript.lcov.reportPaths`)

Co-authored-by: chrismazanek <chrismazanek@users.noreply.github.com>
Co-authored-by: Andreas Hochsteger <andreas@hochsteger.at>
AI-Assisted: true
AI-Tool: Antigravity

Coverage Stats

843 of 946 branches covered (89.11%)

Branch coverage included in aggregate %.

418 of 486 new or added lines in 13 files covered. (86.01%)

14 existing lines in 1 file now uncovered.

8038 of 8303 relevant lines covered (96.81%)

119.34 hits per line