Skip to content

Push Audiences improvements #813

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

Merged
merged 2 commits into from
Jun 11, 2018
Merged

Push Audiences improvements #813

merged 2 commits into from
Jun 11, 2018

Conversation

flovilmart
Copy link
Contributor

  • Fix issue affecting bad requests with audience_limit
  • Adds support for sizing audiences in the dashboard running counts on _Installation table

urlsSeparator = '&';
let promise;
if (!query) {
promise = new Parse.Query('_Audience').get(audienceId, { useMasterKey: true }).then(function(audience) {
Copy link
Contributor Author

Choose a reason for hiding this comment

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

we may wanna add caching for those counts as may be quite expensive on the DB.

Copy link
Contributor

Choose a reason for hiding this comment

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

@flovilmart do we want to add in caching with this PR or do we want to handle this later on?

Copy link
Contributor

Choose a reason for hiding this comment

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

Also if this runs okay on your end this would be great to get in. About time we should put up a dashboard release so we can get past #811 .

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yep, caching would need more work, not required

Copy link
Contributor

Choose a reason for hiding this comment

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

Ehhh, maybe in this case we should cache. Although we could take it as is it would be nice to not have to come back and do that later.

@flovilmart
Copy link
Contributor Author

@montymxb i’d Like to get this one in for the release too

@montymxb montymxb mentioned this pull request Dec 2, 2017
3 tasks
@montymxb
Copy link
Contributor

montymxb commented Dec 2, 2017

Yep yep, just saw this. Sorry I'm behind by a day or so and just going through everything.

@flovilmart flovilmart merged commit 863bc0f into master Jun 11, 2018
beiguancyc pushed a commit to beiguancyc/parse-dashboard that referenced this pull request Jul 10, 2018
* parse:
  Update dependencies to enable Greenkeeper 🌴 (parse-community#865)
  Ensure we traverse the payloadJSON properly (parse-community#861)
  Push Audiences improvements (parse-community#813)
@dplewis dplewis deleted the fix/improper-query-params branch May 9, 2019 21:11
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.

3 participants