-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
SmartyTech Bid Adapter : initial adapter release #9196
Conversation
Hi @preved-medved , your bidder does not satisfy the requirement of having at least 80% test coverage. Please be sure to increase code coverage. To see the coverage run first
and then
|
Hi @musikele. Fixed, sorry for that. |
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.
Check comments please
modules/smartytechBidAdapter.js
Outdated
return bidObject; | ||
}, | ||
|
||
postRequest(endpoint, data) { |
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.
I don't understand the need for this method, it doesn't seem to be called by anybody
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.
LGTM
@preved-medved You may open a PR in the headerbid-expert repository to have their adapter recognized by the Headerbid Expert extension. The PR should be to the bidder patterns file, adding an entry with their adapter's name and the url the adapter uses to send and receive bid responses. |
Docs PR prebid/prebid.github.io#4125 |
* Add new bid adapter for company smartytech * change domain to prod * update unit tests * remove unused code * remove unused code
* Add new bid adapter for company smartytech * change domain to prod * update unit tests * remove unused code * remove unused code
Type of change
Bugfix
Feature
New bidder adapter
Code style update (formatting, local variables)
Refactoring (no functional changes, no api changes)
Build related changes
CI related changes
Does this change affect user-facing APIs or examples documented on http://prebid.org?
Other
Description of change
Other information