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

Skip links on null employer and occupation. #889

Merged
merged 1 commit into from
Oct 23, 2015

Conversation

jmcarp
Copy link
Contributor

@jmcarp jmcarp commented Oct 23, 2015

Since we don't currently expose filters to restrict transctions by null
employer or occupation, we don't have a good way to build links to
itemized browse views for aggregates with null values. This patch omits
links for these aggregate rows.

To verify: browse to a committee detail page, receipts tab, employer or occupation aggregates; there should be the usual links to aggregates for non-null employers and occupations, but no links for null values.

h/t @noahmanger

Since we don't currently expose filters to restrict transctions by null
employer or occupation, we don't have a good way to build links to
itemized browse views for aggregates with null values. This patch omits
links for these aggregate rows.

h/t @noahmanger
@noahmanger
Copy link
Contributor

Just to verify: Null employer and occupations get displayed as N/A in these tables, and the links are still present to /receipts filtered by N/A. Is this right? The back button works in these scenarios.

@jmcarp
Copy link
Contributor Author

jmcarp commented Oct 23, 2015

Null values will continue to be reported as "NOT REPORTED", and they won't have links at all, since there isn't a link we can build that would fetch transactions with null employers or occupations. This is based on Slack discussion yesterday, but happy to revise if there's a better approach.

@noahmanger
Copy link
Contributor

Oh, gotcha. I didn't realize "NOT REPORTED" was different than "N/A".

noahmanger pushed a commit that referenced this pull request Oct 23, 2015
Skip links on null employer and occupation.
@noahmanger noahmanger merged commit 3591d1e into fecgov:develop Oct 23, 2015
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.

2 participants