Hannah Wolfe ed16998461 Restructure Configuration API endpoint ... refs #6421, #6525 - The configuration API endpoint was a bit of an animal: - It's used currently in two ways, once for general config, another for the about page. - These two things are different, and would require different permissions in future. - There was also both a browse and a read version, even though only browse was used. - The response from the browse was being artificially turned into many objects, when its really just one with multiple keys - The new version treats each type of config as a different single object with several keys - The new version therefore only has a 'read' request - A basic read request with no key will return basic config that any client would need - A read request with the about key returns the about config - A read request with a different key could therefore return some other config		2016-02-19 18:49:23 +00:00
..
api	Restructure Configuration API endpoint	2016-02-19 18:49:23 +00:00
model	Merge pull request #6532 from jaswilli/issue-6491	2016-02-18 09:12:06 +00:00
export_spec.js	Removed uneeded jshint comments in order to cleanup the tests	2016-02-17 12:52:43 +00:00
import_spec.js	Removed uneeded jshint comments in order to cleanup the tests	2016-02-17 12:52:43 +00:00
migration_spec.js	Removed uneeded jshint comments in order to cleanup the tests	2016-02-17 12:52:43 +00:00
update_check_spec.js	Removed uneeded jshint comments in order to cleanup the tests	2016-02-17 12:52:43 +00:00