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
..
api/v2	allow anonymous users to GET api routes (#842)	2016-10-26 08:37:23 +08:00
controllers	make synapse permissions depend on topic1 and topic2 (#839)	2016-10-28 11:03:59 +08:00
factories	access request tests (#772)	2016-10-17 10:53:53 -04:00
mailers	access request tests (#772)	2016-10-17 10:53:53 -04:00
models	access request tests (#772)	2016-10-17 10:53:53 -04:00
policies	automatic rubocop updates	2016-09-24 11:00:46 +08:00
schemas	check map#contains matches json schema in spec	2016-02-09 11:20:39 +08:00
support	automatic rubocop updates	2016-09-24 11:00:46 +08:00
rails_helper.rb	automatic rubocop updates	2016-09-24 11:00:46 +08:00
spec_helper.rb	automatic rubocop updates	2016-09-24 11:00:46 +08:00