Hannah Wolfe 17499dbc7b Generate context from channelConfig, not URL ... refs #5091 - makes post context explicit - data.post must be set, rather than post being the default - uses channelConfig to determine the context for a channel (the channel name) rather than basing it off of the URL - updates tests to setup the contexts more clearly, the outcome has not changed Since #6469 req has channelConfig attached to it. We can use req.channelConfig to determine what the context should be for a channel (the channel name) This allows us to remove the hardcoded URLs, and means that custom channels will automatically get their own context. Coupled with removing 'post' from being a default/fallthrough, to being explicitly set, this will reduce potential context errors, as we start to extend the frontend capabilities		2016-03-20 12:59:25 +00:00
..
channels_spec.js	Disambiguate between error code & status code	2016-02-17 15:20:49 +00:00
context_spec.js	Generate context from channelConfig, not URL	2016-03-20 12:59:25 +00:00
error_spec.js	Removed uneeded jshint comments in order to cleanup the tests	2016-02-17 12:52:43 +00:00
fetch-data_spec.js	Removed uneeded jshint comments in order to cleanup the tests	2016-02-17 12:52:43 +00:00
format-response_spec.js	deps: should@8.2.1	2016-02-09 13:39:10 +00:00
index_spec.js	Removed uneeded jshint comments in order to cleanup the tests	2016-02-17 12:52:43 +00:00
templates_spec.js	Removed uneeded jshint comments in order to cleanup the tests	2016-02-17 12:52:43 +00:00