Document multiple sources in listen command#303
Conversation
The `listen` command already supports listening to multiple sources via a comma-separated list and "*" for all sources, but the `-h` help text only described a single required source, making the feature hard to discover. - Update Short/Long description and Usage line to mention one or more sources - Mark the source argument as optional and document the comma-separated list and "*" syntax - Add multi-source and "*" examples - Regenerate REFERENCE.md
alvarp
left a comment
There was a problem hiding this comment.
Check the two comments related to the port, I believe that the examples are broken.
|
|
||
| Forward events from multiple sources to a local server running on port %[1]d: | ||
|
|
||
| hookdeck listen %[1]d shopify,stripe |
There was a problem hiding this comment.
%[1]d here is a Go fmt.Sprintf verb, not a literal — the whole Examples block is built via fmt.Sprintf(..., 3000), so this renders as hookdeck listen 3000 shopify,stripe. It matches the pre-existing examples in the same block (e.g. hookdeck listen %[1]d shopify a few lines up), which also use %[1]d. GitHub only let you comment on the newly-added lines, so the identical older lines aren't flagged. Happy to switch the entire block to a literal 3000 if you'd prefer that for readability, but I left these consistent with the surrounding examples.
Generated by Claude Code
|
|
||
| Forward events from all of your sources: | ||
|
|
||
| hookdeck listen %[1]d '*' |
There was a problem hiding this comment.
Same as above — %[1]d is a fmt.Sprintf placeholder that renders as 3000 (hookdeck listen 3000 '*'), consistent with the rest of the Examples block.
Generated by Claude Code
Summary
Enhanced the
listencommand to support forwarding events from multiple sources simultaneously, in addition to the existing single-source functionality.Changes
[source(s)]instead of[source], indicating support for multiple sourcesImplementation Details
https://claude.ai/code/session_01RpnqJcy3FFXtUQvSnMA8m2