feat: Force user agent in API #184
Merged
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
|
@butteredwaffles may I let you fix the checks ? |
|
Kudos, SonarCloud Quality Gate passed!
|
|
@alexgarel sorry! didn't realize the flake8 lint had several commands under it - should hopefully be fixed now |
|
@butteredwaffles I invited you to our team, so that you will be able to open branches directly on this repository ! |
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.
Description
Forces the user agent to be provided in order to use openfoodfacts.API functions.
Solution
Adds a new field into
APIConfigcalled "user_agent" and ensures it is not empty when passed in. The user agent is passed into the requests the session makes.Related issue(s)