-
Notifications
You must be signed in to change notification settings - Fork 1k
Fix cron trigger documentation links and inline testing instructions #11139
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
Conversation
- Updated documentation links to point to the correct cron triggers page - Inlined instructions for testing cron triggers locally in the error message - Users now see the curl command directly in the warning instead of having to click through to docs Co-Authored-By: Steve Faulkner <southpolesteve@gmail.com>
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
🦋 Changeset detectedLatest commit: 9444d73 The changes in this PR will be included in the next version bump. 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 |
create-cloudflare
@cloudflare/kv-asset-handler
miniflare
@cloudflare/pages-shared
@cloudflare/unenv-preset
@cloudflare/vite-plugin
@cloudflare/vitest-pool-workers
@cloudflare/workers-editor-shared
@cloudflare/workers-utils
wrangler
commit: |
Changed 'Miniflare does not currently trigger scheduled Workers automatically' to 'Scheduled Workers are not automatically triggered during local development' to make the message more user-friendly and avoid referencing internal implementation details. Co-Authored-By: Steve Faulkner <southpolesteve@gmail.com>
…ve messaging - Update curl endpoint from /cdn-cgi/mf/scheduled to /cdn-cgi/handler/scheduled - Replace manual didWarnMiniflareCronSupport flag with logger.once.warn() - Remove 'wrangler dev --local' recommendation since warning appears during dev - Make host/port dynamic using config.initialIp and config.initialPort - Handle IPv6 addresses with brackets and 0.0.0.0/:: as localhost - Update template files to use new endpoint and remove --local flag Co-Authored-By: Steve Faulkner <southpolesteve@gmail.com>
|
Thanks for the feedback! I've addressed all your comments:
All changes have been pushed and are ready for review! |
|
Congratulations @devin-ai-integration[bot], the maintainer of this repository has issued you a holobyte! Here it is: https://holopin.io/holobyte/cmheug8zz007tl804vqtbg8yk This badge can only be claimed by you, so make sure that your GitHub account is linked to your Holopin account. You can manage those preferences here: https://holopin.io/account. |
Devin PR requested by @southpolesteve
Addresses PR feedback on #11139 to improve cron trigger documentation and user-facing messaging.
Changes
Updated endpoint from legacy to current:
/cdn-cgi/mf/scheduled→/cdn-cgi/handler/scheduledthroughout codebasepackages/wrangler/src/dev/miniflare/index.tsnew-worker-scheduled.jsand.ts)Improved warning message UX:
wrangler dev --local" to just show the curl command (since warning appears during dev)didWarnMiniflareCronSupportflag withlogger.once.warn()config.initialIpandconfig.initialPortFixed documentation links:
#test-cron-triggersto#test-cron-triggers-locallyReview Focus Areas
packages/wrangler/src/dev/miniflare/index.ts:830-836): IPv6 detection using.includes(":")- verify this handles all edge cases correctly/cdn-cgi/handler/scheduledis universally correct and won't break existing workflowswrangler dev(without--local) is the correct recommendation for testing cron triggers