-
Notifications
You must be signed in to change notification settings - Fork 31
First pass at data tables for filings on committee pages and /filings #306
Conversation
return anchor.outerHTML; | ||
} | ||
}, | ||
{data: 'committee_name', className: 'min-desktop', orderable: false}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need the committee_name
column here? Won't this be the same for every row?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For the committee page, we don't need committee name, but for the filings query builder we do since you could query across committees. That's why there are two tables. You can see the filings query builder on the front end at /filings
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, I agree- we don't need committee name on the committee page! I can fix that.
Feature/filings tab
@noahmanger the basics are here but it is still looking a bit off. Here are my notes on the progress of this branch:
|
Looking pretty good. A few thoughts:
|
These are great comments
|
Feature/filings tab
URL is not being constructed properly yet.