Allow wildcard event typing with .fromRecord()

[jpwilliams]

Summary

Adds the ability to provide better wildcard event typing in .fromRecord() by changing how name is assigned and overwritten when forming EventSchemas.

The following schema is now valid:

export const schemas = new EventSchemas().fromRecord<{
  "app/blog.post.*":
    | {
        name: "app/blog.post.created";
        data: {
          postId: string;
          authorId: string;
          createdAt: string;
        };
      }
    | {
        name: "app/blog.post.published";
        data: {
          postId: string;
          authorId: string;
          publishedAt: string;
        };
      };
}>();

When creating a function, this allows you to appropriately type narrow the event to pull out the correct data:

inngest.createFunction(
  { id: "my-fn" },
  { event: "app/blog.post.*" },
  async ({ event }) => {
    if (event.name === "app/blog.post.created") {
      console.log("Blog post created at:", event.data.createdAt);
    } else if (event.name === "app/blog.post.published") {
      console.log("Blog post published at:", event.data.publishedAt);
    }
  }
);

Checklist

• Added a docs PR that references this PR
• Added unit/integration tests
• Added changesets if applicable

Related

• Previous method documented in Document wildcard trigger support website#1055

[changeset-bot]

🦋 Changeset detected

Latest commit: 443a121

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
inngest	Patch

Not sure what this means? Click here to learn what changesets are.

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

[djfarrelly]

This is great!