Ghost/core/server/services/route/app-router.js

var ParentRouter = require('./ParentRouter'),
    appRouter = new ParentRouter('apps');

module.exports = appRouter;
Rework route service to prevent circular dependencies (#9229) refs #9192, refs #9178 After trying to progress with current implementation, it became clear that the route service can't control the boot sequence, because then we end up with circular dependencies between the route service and the channel service. The route service now exposes: - a siteRouter - a way for apps to register routes. - ParentRouter base class for other modules to use - the registry ... - moved the default route setup back to site/routes.js 🙈 - moved the parent channel router back to the channel service (this makes way more sense imo) - this structure prevents circular dependencies - split the registry out into it's own thing - fixed-up various bits of tests and comments - DEBUG will print a list of routes 🎉 2017-11-09 16:58:22 +03:00			`var ParentRouter = require('./ParentRouter'),`
			`appRouter = new ParentRouter('apps');`
Wrapped express router & expose from route service (#9206) refs #9192 - Moving towards a centralised concept of routing / routes - The base router now wraps express router, and offers us the features we need - Site Router is the parent router, it gets initialised with all of our default routing - App Router is a sub router for apps - apps register their routes/routers onto it. - TODO: refactor channels subrouter to work this same way - MAYBE: move the app router to the apps service 2017-11-09 13:08:11 +03:00
			`module.exports = appRouter;`