Ensure event payloads are typed as JSON

[jpwilliams]

Summary

Warning

This is a breaking change for some builds.

This PR ensures that, similar to step.run() outputs, event data is also represented as being (de)serialized with JSON, stripping fields such as Date.

There are ongoing discussions on the appropriateness and typing application of middleware-based transformers (see #160), but for now we should make sure that they the typing correctly represents the runtime values.

Even though this is fixing a misrepresentation of an event's data, it could still break builds for users pushing event.data into other formats. Thus we cannot ship this until v4.

Checklist

• Added a docs PR that references this PR N/A Bug fix
• Added unit/integration tests
• Added changesets if applicable

Related

• Add a transformer like trpc #160

[changeset-bot]

⚠️ No Changeset found

Latest commit: bd64e5b

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR