{"action":"created","issue":{"url":"https://api.github.com/repos/awesomefoundation/awesomebits/issues/202","labels_url":"https://api.github.com/repos/awesomefoundation/awesomebits/issues/202/labels{/name}","comments_url":"https://api.github.com/repos/awesomefoundation/awesomebits/issues/202/comments","events_url":"https://api.github.com/repos/awesomefoundation/awesomebits/issues/202/events","html_url":"https://github.com/awesomefoundation/awesomebits/pull/202","id":110818404,"number":202,"title":"Add ability to hide projects","user":{"login":"arsduo","id":48325,"avatar_url":"https://avatars.githubusercontent.com/u/48325?v=3","gravatar_id":"","url":"https://api.github.com/users/arsduo","html_url":"https://github.com/arsduo","followers_url":"https://api.github.com/users/arsduo/followers","following_url":"https://api.github.com/users/arsduo/following{/other_user}","gists_url":"https://api.github.com/users/arsduo/gists{/gist_id}","starred_url":"https://api.github.com/users/arsduo/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/arsduo/subscriptions","organizations_url":"https://api.github.com/users/arsduo/orgs","repos_url":"https://api.github.com/users/arsduo/repos","events_url":"https://api.github.com/users/arsduo/events{/privacy}","received_events_url":"https://api.github.com/users/arsduo/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/awesomefoundation/awesomebits/labels/in%20progress","name":"in progress","color":"ededed"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":20,"created_at":"2015-10-10T21:40:31Z","updated_at":"2015-11-01T19:09:54Z","closed_at":null,"pull_request":{"url":"https://api.github.com/repos/awesomefoundation/awesomebits/pulls/202","html_url":"https://github.com/awesomefoundation/awesomebits/pull/202","diff_url":"https://github.com/awesomefoundation/awesomebits/pull/202.diff","patch_url":"https://github.com/awesomefoundation/awesomebits/pull/202.patch"},"body":"Our chapter, like many others, gets a lot of applications that aren't valid -- people asking for money to fix their homes, start a business, or just submitting the same application twice. This seems to have been a problem for as long as AF has been going (issue #37 was opened back in 2012).\r\n\r\nAfter talking it over with the Chicago chapter, this pull request implements an \"Hide\" button. If a trustee or dean sees a grant they don't think is valid, they can save the rest of their chapter time by clicking on \"Hide\" and entering a reason they don't think the grant is valid.\r\n\r\nTo keep everything transparent, hidden applications don't disappear completely -- they show up in abbreviated form in the list with who hid them, when, and why. If another trustee disagrees, they can hit the \"unhide\" button. Additionally, if you click through to the individual project page, you can see all the details for the project.\r\n\r\nScreenshots:\r\n\r\n_Prompt shows up for each entry:_\r\n<img width=\"1258\" alt=\"bildschirmfoto 2015-10-10 um 16 32 15\" src=\"https://cloud.githubusercontent.com/assets/48325/10413404/4a28c716-6f6d-11e5-9f80-8207fa7420fa.png\">\r\n\r\n_Entering a reason to hide:_\r\n<img width=\"1258\" alt=\"bildschirmfoto 2015-10-10 um 16 32 29\" src=\"https://cloud.githubusercontent.com/assets/48325/10413406/61311a8a-6f6d-11e5-9c37-51455b604193.png\">\r\n\r\n_After hiding, you're brought back to the same spot and can see the hidden project:_\r\n<img width=\"1258\" alt=\"bildschirmfoto 2015-10-10 um 16 33 28\" src=\"https://cloud.githubusercontent.com/assets/48325/10413411/7a85e7a4-6f6d-11e5-8a63-6157499675c8.png\">\r\n\r\n_In the individual view, you get the full details:_\r\n<img width=\"1258\" alt=\"bildschirmfoto 2015-10-10 um 16 33 33\" src=\"https://cloud.githubusercontent.com/assets/48325/10413416/8e485484-6f6d-11e5-8ddb-80e22e3774d7.png\">\r\n\r\n_If you unhide, you see the whole project again:_\r\n<img width=\"1258\" alt=\"bildschirmfoto 2015-10-10 um 16 33 37\" src=\"https://cloud.githubusercontent.com/assets/48325/10413419/95d2e2be-6f6d-11e5-966b-86ea14974c16.png\">\r\n"},"comment":{"url":"https://api.github.com/repos/awesomefoundation/awesomebits/issues/comments/152852540","html_url":"https://github.com/awesomefoundation/awesomebits/pull/202#issuecomment-152852540","issue_url":"https://api.github.com/repos/awesomefoundation/awesomebits/issues/202","id":152852540,"user":{"login":"jcn","id":2909,"avatar_url":"https://avatars.githubusercontent.com/u/2909?v=3","gravatar_id":"","url":"https://api.github.com/users/jcn","html_url":"https://github.com/jcn","followers_url":"https://api.github.com/users/jcn/followers","following_url":"https://api.github.com/users/jcn/following{/other_user}","gists_url":"https://api.github.com/users/jcn/gists{/gist_id}","starred_url":"https://api.github.com/users/jcn/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jcn/subscriptions","organizations_url":"https://api.github.com/users/jcn/orgs","repos_url":"https://api.github.com/users/jcn/repos","events_url":"https://api.github.com/users/jcn/events{/privacy}","received_events_url":"https://api.github.com/users/jcn/received_events","type":"User","site_admin":false},"created_at":"2015-11-01T19:09:54Z","updated_at":"2015-11-01T19:09:54Z","body":"Another comment (and I hope these aren't too annoying - I truly appreciate the functionality here and think it's a great feature): how big a pain would it be to do the hiding/unhiding in an Ajax call. From a user interaction perspective, reloading the page on every hide, especially in the use case you describe where there are a lot of projects to hide in a given month, is going to be tedious for the hider. In addition, with pagination, if you're on page 2 and you click hide you're going to be bounced back to page 1, which is going to be a jarring experience. The code for marking a winner and shortlisting a project is a pretty good mechanism I think, and could apply pretty well:\r\n\r\nhttps://github.com/awesomefoundation/awesomebits/blob/master/app/assets/javascripts/projects.js.coffee\r\n\r\nThe only issue is that the way those work is they apply a class to the surrounding div which changes the behavior of that div. I think this might work here, but it would break the other thing I'd asked you to do earlier with breaking the display into 2 partials. \r\n\r\nThis is, of course, a failure on my part to properly review the code in the first place, and I apologize for that. I can take a stab at it myself and make the appropriate changes if it's too annoying to have to revert these changes. I'm just thinking that from a user-perspective, this makes for a much better experience.\r\n\r\nAlso happy to discuss on slack if that'd be easier."}}