Should we have a default catchall/fallback job handler? #127
wanghanlin
started this conversation in
Ideas
Replies: 1 comment 1 reply
-
Feel free to create a PR that adds this functionality. Make sure to update the readme and tests. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
In stripe cli for local webhook development, stripe will proxy and forward all event types, which get write into database without a function to process it.
Some time, we could enable more event types than needed on stripe console as well.
Should we have a default job handler built-in or open for integration that do nothing but mark those extra webhook calls that write into DB as success
Suggestion:
https://github.com/spatie/laravel-stripe-webhooks/blob/main/src/ProcessStripeWebhookJob.php#L35
change the default
''
to a new Job class built-in package, or have an option in configstripe-webhooks.jobs.fallback
or something likestripe-webhooks.default_jobs
for developer to code for a fallback handlerBeta Was this translation helpful? Give feedback.
All reactions