ghost/core/frontend/web/routes.js

const debug = require('@tryghost/debug')('frontend:routes');
const routing = require('../services/routing');

/**
 *
 * @param {import('../services/routing/router-manager').RouterConfig} routerConfig
 * @returns {import('express').Router}
 */
module.exports = function siteRoutes(routerConfig) {
    debug('site Routes', routerConfig);
    return routing.routerManager.init(routerConfig);
};
Removed versioned confg from URL Service refs: https://github.com/TryGhost/Toolbox/issues/228 refs: https://github.com/TryGhost/Toolbox/issues/229 - we are getting rid of the concept of having multiple api versions in a single ghost install - this means the url service doesn't need to be versioned any more 2022-04-06 13:03:22 +01:00			`const debug = require('@tryghost/debug')('frontend:routes');`
Moved server/web/site to frontend/web - we're slowly trying to draw the lines between the backend and the frontend correctly - these files deal only with serving the frontend so they should live there - there are lots of mixed requires in these files, so having them in the right place makes that clear 2021-10-16 16:26:05 +01:00			`const routing = require('../services/routing');`
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 13:58:22 +00:00
Moved frontend reloading logic into bridge - following on from removing api versioning logic from the frontend, it's possible to make more sense of what's happening - this commit first introduces a proper jsdoc'd object that gets passed through the frontent load & reload flow - that object contains the urlService and optionally our routeSettings processed from routes.yaml - additionally, we were passing around a start boolean, which told the routerManager whether to just init, or init+start - with this refactor, we always pass in the routeSettings when we want to do init+start, so we no longer need a boolean - The refactor itself moves logic from the reload function in site.js and urlservice + routesettings fetching logic from routes.js into the reloadFrontend function in bridge.js. - This makes it clearer to see what happens when we call reloadFrontend. - This commit also makes it clearer to see what is happening with the route settings, where they are needed and why - Ideally we'd also clean up the weird dupliated logic and somewhat unnecessary routes.js file 2022-04-13 11:09:22 +01:00			`/**`
			`*`
			`* @param {import('../services/routing/router-manager').RouterConfig} routerConfig`
			`* @returns {import('express').Router}`
			`*/`
			`module.exports = function siteRoutes(routerConfig) {`
			`debug('site Routes', routerConfig);`
			`return routing.routerManager.init(routerConfig);`
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 13:58:22 +00:00			`};`