Skip to content

Conversation

@EricGhildyal
Copy link
Contributor

Also refactor SDK to no longer require a worker name

@EricGhildyal EricGhildyal self-assigned this Jun 16, 2025
Copy link
Contributor

@RobbieMcKinstry RobbieMcKinstry left a comment

Choose a reason for hiding this comment

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

I can't review all of the files because of the GitHub outage, but I'll come back later .

/// This is the Cloudflare account id
account_id: String,
/// The name of the Cloudflare worker
worker_name: String,
Copy link
Contributor

Choose a reason for hiding this comment

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

Can you explain why you don't provide the worker name as a struct field anymore, and instead pass it in at each call site? I don't mean explain it in a code comment, just explain in here in PR review so I have a better understanding of the code moving forward. Thank you!

Copy link
Contributor Author

Choose a reason for hiding this comment

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

We use the CloudflareClient in multi init now, where we're performing actions that don't have a worker name yet (ex: when we're listing all available Workers).

I remember us talking about this when building CF support and figured that we'd refactor later on.

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