#10924 0c8f5ba
Thanks @eddeee888! - Fix profiler output not being written to the
filesystem in watch mode (--profile --watch)
The profiler trace was only written on the non-watch code path, after the watch-mode early return,
so a profiled watch session never produced a codegen-*.json file.
The profiler now writes a fresh trace file after the initial run and after every rebuild, with
each file containing only that run's events. A failed rebuild does not produce a trace and its
events are discarded so they don't leak into the next successful run.
The Profiler now owns its own trace lifecycle:
a new clear() method starts a new trace
a new outputName property provides the filename for the current trace (null for the noop
profiler)
filename generation was removed from CodegenContext
This PR contains the following updates:
| Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) |
|---|---|---|---|
| [@graphql-codegen/cli](https://github.com/dotansimha/graphql-code-generator) ([source](https://github.com/dotansimha/graphql-code-generator/tree/HEAD/packages/graphql-codegen-cli)) | [`7.3.0` → `7.3.1`](https://renovatebot.com/diffs/npm/@graphql-codegen%2fcli/7.3.0/7.3.1) |  |  |
---
### Release Notes
<details>
<summary>dotansimha/graphql-code-generator (@​graphql-codegen/cli)</summary>
### [`v7.3.1`](https://github.com/dotansimha/graphql-code-generator/blob/HEAD/packages/graphql-codegen-cli/CHANGELOG.md#731)
[Compare Source](https://github.com/dotansimha/graphql-code-generator/compare/@graphql-codegen/cli@7.3.0...@graphql-codegen/cli@7.3.1)
##### Patch Changes
- [#​10924](https://github.com/dotansimha/graphql-code-generator/pull/10924)
[`0c8f5ba`](https://github.com/dotansimha/graphql-code-generator/commit/0c8f5ba763b6cfb714814d1666f066dbdb91ef02)
Thanks [@​eddeee888](https://github.com/eddeee888)! - Fix profiler output not being written to the
filesystem in watch mode (`--profile --watch`)
The profiler trace was only written on the non-watch code path, after the watch-mode early return,
so a profiled watch session never produced a `codegen-*.json` file.
The profiler now writes a fresh trace file after the initial run and after every rebuild, with
each file containing only that run's events. A failed rebuild does not produce a trace and its
events are discarded so they don't leak into the next successful run.
The `Profiler` now owns its own trace lifecycle:
- a new `clear()` method starts a new trace
- a new `outputName` property provides the filename for the current trace (`null` for the noop
profiler)
- filename generation was removed from `CodegenContext`
- Updated dependencies
\[[`0c8f5ba`](https://github.com/dotansimha/graphql-code-generator/commit/0c8f5ba763b6cfb714814d1666f066dbdb91ef02)]:
- [@​graphql-codegen/plugin-helpers](https://github.com/graphql-codegen/plugin-helpers)@​7.2.1
</details>
---
### Configuration
📅 **Schedule**: (UTC)
- Branch creation
- At any time (no schedule defined)
- Automerge
- At any time (no schedule defined)
🚦 **Automerge**: Enabled.
♻ **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 **Ignore**: Close this PR and you won't be reminded about this update again.
---
- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box
---
This PR has been generated by [Mend Renovate CLI](https://github.com/renovatebot/renovate).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0NC4zMS4wIiwidXBkYXRlZEluVmVyIjoiNDQuMzEuMCIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOltdfQ==-->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
This PR contains the following updates:
7.3.0→7.3.1Release Notes
dotansimha/graphql-code-generator (@graphql-codegen/cli)
v7.3.1Compare Source
Patch Changes
#10924
0c8f5baThanks @eddeee888! - Fix profiler output not being written to the
filesystem in watch mode (
--profile --watch)The profiler trace was only written on the non-watch code path, after the watch-mode early return,
so a profiled watch session never produced a
codegen-*.jsonfile.The profiler now writes a fresh trace file after the initial run and after every rebuild, with
each file containing only that run's events. A failed rebuild does not produce a trace and its
events are discarded so they don't leak into the next successful run.
The
Profilernow owns its own trace lifecycle:clear()method starts a new traceoutputNameproperty provides the filename for the current trace (nullfor the noopprofiler)
CodegenContextUpdated dependencies
[
0c8f5ba]:Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate CLI.