Skip to content
This repository has been archived by the owner on Dec 23, 2017. It is now read-only.

Fixing candidate pages #31

Merged
merged 33 commits into from
Feb 11, 2015
Merged

Conversation

theresaanna
Copy link
Contributor

This request primarily fixes candidate pages. As of now, they are not rendering properly when using the api_performance branches.

It also incorporates some rework of render_page, which made sense in the context of some of this work.

I am under no illusions that these are the most elegant solutions ever. These are patches so that people can use the candidate page. I figure that things are going to change a lot once the API work is done, so I am not fretting the solutions for the moment.

Right now, totals data for committees that are not primary aren't showing. I thought, since these pages are broken, I'd get this in regardless. Unsure if its an API issue, front end issue or both.

@@ -94,6 +94,9 @@ def map_totals(t):
from the 'totals' endpoint for use on candidat
and committee pages
"""
if not t['results'][0].get('reports') and not t['results'][0].get('totals'):
Copy link
Contributor

Choose a reason for hiding this comment

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

Should this be an or?

@cmc333333
Copy link
Contributor

👍 Python stuff at the top -- there's a lot of diff associated with the merges, though

LindsayYoung added a commit that referenced this pull request Feb 11, 2015
@LindsayYoung LindsayYoung merged commit a5f2586 into api_performance Feb 11, 2015
@LindsayYoung LindsayYoung deleted the fixing-candidate-pages branch February 11, 2015 18:59
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants