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

Expose null sort controls to user. #325

Merged
merged 5 commits into from
Jul 13, 2015

Conversation

jmcarp
Copy link
Contributor

@jmcarp jmcarp commented Jul 9, 2015

Instead of automatically hiding rows with NULL values on sorted columns, allow users to control whether nulls are hidden or not. Any improvements on language / look and feel / default behavior welcome @LindsayYoung @noahmanger.

@@ -60,7 +60,7 @@ before_script:
- cd openFEC
- git checkout $FEC_BRANCH
- psql -c 'create database cfdm_test' -U postgres
- psql -f data/subset.sql cfdm_test -U postgres
- pg_restore --dbname cfdm_test data/subset.dump --no-acl --no-owner
Copy link
Contributor

Choose a reason for hiding this comment

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

Is there a reason this was changed in this review?

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, we deleted a bunch of old code from the API recently, which included the old subset. This code uses the current subset.

@msecret
Copy link
Contributor

msecret commented Jul 10, 2015

This looks good from a code perspective, will wait on @noahmanger @LindsayYoung for UI review.

@LindsayYoung
Copy link
Contributor

I think it is important for the user to understand that nulls are being filtered out. Otherwise, the sort will change the count and things will seem to appear and disappear.

(I talked about this with Josh, but wanted to document it here)

@noahmanger
Copy link
Contributor

Sorry, just looking at this now. This seems really tricky. Important, but tricky. First question I have is whether it might make more sense to have this in the box above the table where the pagination controls are. It's not really a filter in the same way the others are filters because it always changes depending on which column you're sorting. Once we move the "Show" / "Hide Filters" button from that box too we'll have more space.

The second question is around language. What about simply "Hide results with missing values when sorting" ? Or something along those lines?

@jmcarp
Copy link
Contributor Author

jmcarp commented Jul 13, 2015

@noahmanger both of those changes sound good to me. I'll update the patch unless folks want to discuss more. @LindsayYoung does this sound good to you?

@LindsayYoung
Copy link
Contributor

LindsayYoung commented Jul 13, 2015 via email

@jmcarp
Copy link
Contributor Author

jmcarp commented Jul 13, 2015

OK, I'm putting the revised null sort control right above the table. LMK if anything else should change before merge.
screen shot 2015-07-13 at 2 32 35 pm

@noahmanger
Copy link
Contributor

Oh sorry, it should be in that same box with the pagination controls. But otherwise, looks good!

@jmcarp
Copy link
Contributor Author

jmcarp commented Jul 13, 2015

OK, moved. @noahmanger or @msecret, feel free to continue fiddling with layout. This may also be good enough to merge and update with future PRs.

@noahmanger
Copy link
Contributor

Looks good to me. Yeah, I think we can move it once the new filter sidebar is merged. Looks like the tests ran into a snag, so I just restarted to see if that helps.

@noahmanger
Copy link
Contributor

Huh. It's throwing this error: The command "python manage.py update_schemas" failed and exited with 1 during .

@jmcarp
Copy link
Contributor Author

jmcarp commented Jul 13, 2015

Blah. I'll look at the tests and update here when they're fixed. The error probably isn't related to this patch.

msecret pushed a commit that referenced this pull request Jul 13, 2015
Expose null sort controls to user.
@msecret msecret merged commit 80347ea into fecgov:develop Jul 13, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants