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

Max_engagement value doesn't exist on new posts. #10

Open
ryanburnette opened this issue Dec 8, 2012 · 1 comment
Open

Max_engagement value doesn't exist on new posts. #10

ryanburnette opened this issue Dec 8, 2012 · 1 comment
Assignees
Labels

Comments

@ryanburnette
Copy link
Collaborator

I thought about it and for sorting purposes there actually does need to be a max_engagement value for new posts. To be clear, there should never be a situation where a post has a current_engagement value without also having a max_engagement value.

This only effects sorting, so it's not super critical, but we should fix it in the next release.

@ghost ghost assigned JerresonJ Dec 8, 2012
@ryanburnette
Copy link
Collaborator Author

Did you 1.2.0 updates address this at all? If not it's fine. We can do this in 1.2.1. Let me know.

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

No branches or pull requests

2 participants