Devin Howard e49e5c258a make synapse permissions depend on topic1 and topic2 (#839) ... * deep change to synapse policy - is this ok? * make synapse policy resilient to nil topic1/topic2/map * use a transaction to handle authorization vs invalid record in synapse controller * more synapse controller tests * inline documentation * fix policy(Synapse).create?		2016-10-28 11:03:59 +08:00
..
application_policy.rb	automatic rubocop updates	2016-09-24 11:00:46 +08:00
explore_policy.rb	explore controller spec	2016-09-25 23:25:38 +08:00
hack_policy.rb	hack to get the <title> tag when importing a url, without CORS issues	2016-09-25 22:50:16 +08:00
main_policy.rb	make requestinvite controller method explicit	2016-09-28 22:29:53 +08:00
map_policy.rb	access requests (#762)	2016-10-16 20:22:00 -04:00
mapping_policy.rb	multiple policy issues (#771)	2016-10-17 01:20:48 -04:00
message_policy.rb	multiple policy issues (#771)	2016-10-17 01:20:48 -04:00
metacode_policy.rb	rubocop + allow unauthed users to see all users	2016-10-04 22:51:21 +08:00
search_policy.rb	pull search routes into their own controller	2016-09-28 22:29:53 +08:00
synapse_policy.rb	make synapse permissions depend on topic1 and topic2 (#839)	2016-10-28 11:03:59 +08:00
token_policy.rb	token policy fix	2016-10-13 15:21:27 +08:00
topic_policy.rb	allow anonymous users to GET api routes (#842)	2016-10-26 08:37:23 +08:00
user_policy.rb	rubocop + allow unauthed users to see all users	2016-10-04 22:51:21 +08:00