Skip to content
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

Update emoteevBidAdapter.js #3928

Merged
merged 8 commits into from
Jul 1, 2019

Conversation

piotr-yuxuan
Copy link
Contributor

@piotr-yuxuan piotr-yuxuan commented Jun 19, 2019

Type of change

  • Feature
  • Refactoring (no functional changes, no api changes)
  • Affects user-facing API (doc pull request)

Description of change

Retrieve various data from the adapter configuration, and ensure they are properly formatted:

  • GDPR vendor consent
  • Metadata: intended to be used as an ID for external partners
  • Context: describe the context of the current ad unit

Test coverage for emoteevBidAdapter.js:

  • Statements 94.83%
  • Branches 98.39%
  • Functions 100%
  • Lines 94.34%

@snapwich
Copy link
Collaborator

snapwich commented Jun 19, 2019

just noticed this pull-request. could you either cherry-pick the changes from #3932 or implement some other solution (that involves not directly importing another module). Thanks

@piotr-yuxuan piotr-yuxuan force-pushed the emoteev-gdpr-metadata-context branch from 03a15ec to 36f93c0 Compare June 21, 2019 13:12
snapwich and others added 2 commits June 21, 2019 15:31
Retrieve various data from the adapter configuration, and ensure they
are properly formatted:
- GDPR vendor consent
- Metadata: intended to be used as an ID for external partners
- Context: describe the context of the current ad unit

Test coverage for emoteevBidAdapter.js:
- Statements 94.83%
- Branches 98.39%
- Functions 100%
- Lines 94.34%

fixup! Update emoteevBidAdapter.js
@piotr-yuxuan piotr-yuxuan force-pushed the emoteev-gdpr-metadata-context branch from 36f93c0 to b97a9b0 Compare June 21, 2019 13:31
@piotr-yuxuan
Copy link
Contributor Author

@snapwich sure, no problem. Does it suit you? Also, please feel free to close the other PR.

@piotr-yuxuan piotr-yuxuan marked this pull request as ready for review June 25, 2019 12:30
Copy link
Contributor

@mike-chowla mike-chowla left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@mike-chowla mike-chowla merged commit be76682 into prebid:master Jul 1, 2019
VideoReach pushed a commit to VideoReach/Prebid.js that referenced this pull request Aug 1, 2019
* Update emoteevBidAdapter.js

Retrieve various data from the adapter configuration, and ensure they
are properly formatted:
- GDPR vendor consent
- Metadata: intended to be used as an ID for external partners
- Context: describe the context of the current ad unit

Test coverage for emoteevBidAdapter.js:
- Statements 94.83%
- Branches 98.39%
- Functions 100%
- Lines 94.34%

fixup! Update emoteevBidAdapter.js

* remove pubCommonId import from emoteevBidAdapter

* Format indentation

* More detailed integration page example

* Rename attribute to externalId

* Simplify names of constants

* Minor tweak

* Update context value
sa1omon pushed a commit to gamoshi/Prebid.js that referenced this pull request Nov 28, 2019
* Update emoteevBidAdapter.js

Retrieve various data from the adapter configuration, and ensure they
are properly formatted:
- GDPR vendor consent
- Metadata: intended to be used as an ID for external partners
- Context: describe the context of the current ad unit

Test coverage for emoteevBidAdapter.js:
- Statements 94.83%
- Branches 98.39%
- Functions 100%
- Lines 94.34%

fixup! Update emoteevBidAdapter.js

* remove pubCommonId import from emoteevBidAdapter

* Format indentation

* More detailed integration page example

* Rename attribute to externalId

* Simplify names of constants

* Minor tweak

* Update context value
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants