User-Agent should include receiver type
Open
Nobody has claimed this yet.
enhancement
semver:patch
- Dominant language
- TypeScript
- Stars
- 2.9k
- Forks
- 445
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 28
Description
Description
We should start to include the receiver type (HttpReceiver, SocketModeReceiver, AwsLambdaReceiver, ExpressReceiver) in the user-agent string. This would allow us to understand the adoption of each receiver and prioritize missing features based on usage.
What type of issue is this? (place an x in one of the [ ])
- bug
- enhancement (feature request)
- question
- documentation related
- example code related
- testing related
- discussion
Requirements (place an x in each of the [ ])
- I've read and understood the Contributing guidelines and have done my best effort to follow them.
- I've read and agree to the Code of Conduct.
- I've searched for any related issues and avoided creating a duplicate issue.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating where Bolt's user-agent string is assembled and where HttpReceiver, SocketModeReceiver, AwsLambdaReceiver, and ExpressReceiver are defined. Confirm how receiver identity is available at that point, then verify that the resulting user-agent identifies each receiver type.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100