feat: allow configuration of User-Agent for client #427
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
programmer04
force-pushed
the
introduce-user-agent
branch
3 times, most recently
from
c4d4af1
to
36907dd
Compare
programmer04
force-pushed
the
introduce-user-agent
branch
from
36907dd
to
2a4dd70
Compare
mlavacca
approved these changes
Mar 26, 2024
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
Setting a
User-Agentheader for each request is a good practice. This PR introduces a straightforward way to configure it.Furthermore, fix all the stuff that prevents linting from passing.
Which issue this PR fixes:
Required for