Skip to content

Conversation

@tzengerink
Copy link
Contributor

@tzengerink tzengerink commented Dec 5, 2017

Thanks to @gvisniuc the Python client is close to supporting Campaigns for Apps 🎉

@Rifinio, @spirosikmd and @shuisman could you guys review the changes?

George Visniuc and others added 2 commits December 5, 2017 15:47
The Readme did not reference the Campaigns for Apps functionality yet.
Also the headers within the Readme were not rendered properly.
@coveralls
Copy link

coveralls commented Dec 5, 2017

Coverage Status

Coverage remained the same at 78.182% when pulling 86802ff on campaign-for-apps into 8701fdc on master.

Copy link
Contributor

@spirosikmd spirosikmd left a comment

Choose a reason for hiding this comment

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

LGTM! Would be nice to set up tests!

Copy link

@Rifinio Rifinio left a comment

Choose a reason for hiding this comment

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

Nice

Added a couple of tests to make sure the newly added resources are
considered valid. While doing so did a minor refactor.
@coveralls
Copy link

coveralls commented Dec 6, 2017

Coverage Status

Coverage increased (+0.4%) to 78.571% when pulling b2702c4 on campaign-for-apps into 8701fdc on master.

After adding support for Campaigns for Apps a new version has to be
tagged and published.
@coveralls
Copy link

coveralls commented Dec 6, 2017

Coverage Status

Coverage increased (+0.4%) to 78.571% when pulling 8cb05b9 on campaign-for-apps into 8701fdc on master.

@tzengerink tzengerink merged commit dbb4929 into master Dec 12, 2017
@tzengerink tzengerink deleted the campaign-for-apps branch December 12, 2017 12:01
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.

5 participants