After adding the dataclass in-place mutation warning in PR #10650, running tests in core-integrations surfaces multiple in-repo usages where we still mutate dataclass instances in place.
We should replace these with dataclasses.replace (or other non-mutating patterns) to avoid warnings and unintended side effects.
Actions
- running tests
- catching warnings,
- fixing the mutating behaviour.
After adding the dataclass in-place mutation warning in PR #10650, running tests in core-integrations surfaces multiple in-repo usages where we still mutate dataclass instances in place.
We should replace these with
dataclasses.replace(or other non-mutating patterns) to avoid warnings and unintended side effects.Actions