Skip to content

add types for event-subscriptions #3814

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Conversation

sdnts
Copy link

@sdnts sdnts commented Mar 27, 2025

Event Subscriptions let you receive events about other CF products as messages on to a Queue. I'm unsure what other context you all need to be able to review this, but I'm happy to provide it.

WIP Docs change: cloudflare/cloudflare-docs#21197

@sdnts sdnts requested a review from a team as a code owner March 27, 2025 17:14
Copy link

github-actions bot commented Mar 27, 2025

All contributors have signed the CLA ✍️ ✅
Posted by the CLA Assistant Lite bot.

@sdnts
Copy link
Author

sdnts commented Mar 27, 2025

@jbwcloudflare
Copy link
Contributor

this looks pretty solid to me!

@sdnts
Copy link
Author

sdnts commented Mar 27, 2025

I have read the CLA Document and I hereby sign the CLA

@sdnts
Copy link
Author

sdnts commented Mar 27, 2025

recheck

github-actions bot added a commit that referenced this pull request Mar 27, 2025
Service extends string,
Type extends string,
Source,
Payload = {},
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this should probably default to Record<string, never> instead? (assuming this is meant to be an empty object)

Comment on lines +37 to +42
type SubscriptionEventSourceWorkflows = {
workflowId: string;
workflowName: string;
versionId: string;
instanceId: string;
};
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's a bit weird that workflows has a helper for this, but superSlurper doesn't. Since this type will be exposed to users, I wonder if we should inline it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants