-
-
Notifications
You must be signed in to change notification settings - Fork 233
Add client info to clone NREPL request #2774
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
Add client info to clone NREPL request #2774
Conversation
✅ Deploy Preview for calva-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
74cf585 to
45d8eb2
Compare
45d8eb2 to
6a7bfbb
Compare
CHANGELOG.md
Outdated
|
|
||
| ## [Unreleased] | ||
|
|
||
| - [Add client info to nrepl clone request](https://github.com/BetterThanTomorrow/calva/pull/2774) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We want this to link to an issue which has the problem description. So that users curious about a change quickly can find out why it was made.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done!
|
Now there are Prettier complaints and also you need to merge/rebase in latest |
|
Done @PEZ |
What has changed?
As discussed here, we are adding nREPL client information to be able to provide metrics about the client of the nREPL.
Related to nrepl/nrepl#370
Fixes #2776
My Calva PR Checklist
I have:
devbranch. (Or have specific reasons to target some other branch.)published. (Sorry for the nagging.)[Unreleased]entry inCHANGELOG.md, linking the issue(s) that the PR is addressing.npm run prettier-format)npm run eslintbefore creating your PR, or runnpm run eslint-watchto eslint as you go).Ping @PEZ, @bpringe, @corasaurus-hex, @Cyrik