Skip to content

Conversation

@amandasteinhauer
Copy link
Contributor

@amandasteinhauer amandasteinhauer commented Jan 19, 2026

TL;DR

Added support for tracking transcript property changes in SetStepLog type.

What changed?

Extended the SetStepLog type to include an optional changedTranscriptProperties field, which is a record mapping property names to their string values. This allows for tracking changes to transcript properties during set operations.

How to test?

  1. Use the updated SetStepLog type in a component that handles transcript property changes
  2. Verify that the changedTranscriptProperties field can be populated with a record of property name/value pairs
  3. Ensure that existing code using SetStepLog continues to work as expected since the new field is optional

Why make this change?

This change enables more detailed logging of transcript property changes during set operations, which improves debugging capabilities and provides better visibility into how transcript properties are being modified during runtime.

@linear
Copy link

linear bot commented Jan 19, 2026

Copy link
Contributor Author

This stack of pull requests is managed by Graphite. Learn more about stacking.

@amandasteinhauer amandasteinhauer marked this pull request as ready for review January 19, 2026 20:02
@sonarqubecloud
Copy link

Copy link
Contributor Author

bors r+

bors-vf bot pushed a commit that referenced this pull request Jan 20, 2026
### TL;DR

Added support for tracking transcript property changes in `SetStepLog` type.

### What changed?

Extended the `SetStepLog` type to include an optional `changedTranscriptProperties` field, which is a record mapping property names to their string values. This allows for tracking changes to transcript properties during set operations.

### How to test?

1. Use the updated `SetStepLog` type in a component that handles transcript property changes
2. Verify that the `changedTranscriptProperties` field can be populated with a record of property name/value pairs
3. Ensure that existing code using `SetStepLog` continues to work as expected since the new field is optional

### Why make this change?

This change enables more detailed logging of transcript property changes during set operations, which improves debugging capabilities and provides better visibility into how transcript properties are being modified during runtime.
@bors-vf
Copy link

bors-vf bot commented Jan 20, 2026

Pull request successfully merged into master.

Build succeeded:

@bors-vf bors-vf bot changed the title feat: include transcript properties in setv3 logging (COR-9466) [Merged by Bors] - feat: include transcript properties in setv3 logging (COR-9466) Jan 20, 2026
@bors-vf bors-vf bot closed this Jan 20, 2026
@bors-vf bors-vf bot deleted the amanda/debug-logging-setv3-transcript-properties/COR-9466 branch January 20, 2026 16:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants