Hannah Wolfe ae2f34c910 Split post lookup out of frontend controller ... no issue - move the post lookup functionality into its own file - handle the pre and post lookup checks to verify that we found the correct post - checking that the URL matches handles checking that a post looked up with pagePermalink is a page - all cases where there is no match throws a 404 directly, this could just call next() ?		2016-05-05 15:53:17 +02:00
..
channel-config.js	Make frontend routing dynamic & driven by channels	2016-02-15 15:57:20 +00:00
channels.js	Make frontend routing dynamic & driven by channels	2016-02-15 15:57:20 +00:00
context.js	Generate context from channelConfig, not URL	2016-03-20 12:59:25 +00:00
error.js	Split helper functions from frontend controller	2015-10-22 18:46:58 +01:00
fetch-data.js	Don't include app fields	2016-02-11 15:03:33 +00:00
format-response.js	Switch frontend controller to use new filter param	2015-10-26 09:40:19 +00:00
index.js	Split post lookup out of frontend controller	2016-05-05 15:53:17 +02:00
post-lookup.js	Split post lookup out of frontend controller	2016-05-05 15:53:17 +02:00
render-channel.js	Make frontend routing dynamic & driven by channels	2016-02-15 15:57:20 +00:00
secure.js	Split helper functions from frontend controller	2015-10-22 18:46:58 +01:00
templates.js	Unify code for picking a template to render with	2015-12-01 12:05:46 +08:00