✨Dynamic Routing Beta (#9596)
refs #9601
### Dynamic Routing
This is the beta version of dynamic routing.
- we had a initial implementation of "channels" available in the codebase
- we have removed and moved this implementation
- there is now a centralised place for dynamic routing - server/services/routing
- each routing component is represented by a router type e.g. collections, routes, static pages, taxonomies, rss, preview of posts
- keep as much as possible logic of routing helpers, middlewares and controllers
- ensure test coverage
- connect all the things together
- yaml file + validation
- routing + routers
- url service
- sitemaps
- url access
- deeper implementation of yaml validations
- e.g. hard require slashes
- ensure routing hierarchy/order
- e.g. you enable the subscriber app
- you have a custom static page, which lives under the same slug /subscribe
- static pages are stronger than apps
- e.g. the first collection owns the post it has filtered
- a post cannot live in two collections
- ensure apps are still working and hook into the routers layer (or better said: and register in the routing service)
- put as much as possible comments to the code base for better understanding
- ensure a clean debug log
- ensure we can unmount routes
- e.g. you have a collection permalink of /:slug/ represented by {globals.permalink}
- and you change the permalink in the admin to dated permalink
- the express route get's refreshed from /:slug/ to /:year/:month/:day/:slug/
- unmount without server restart, yey
- ensure we are backwards compatible
- e.g. render home.hbs for collection index if collection route is /
- ensure you can access your configured permalink from the settings table with {globals.permalink}
### Render 503 if url service did not finish
- return 503 if the url service has not finished generating the resource urls
### Rewrite sitemaps
- we have rewritten the sitemaps "service", because the url generator does no longer happen on runtime
- we generate all urls on bootstrap
- the sitemaps service will consume created resource and router urls
- these urls will be shown on the xml pages
- we listen on url events
- we listen on router events
- we no longer have to fetch the resources, which is nice
- the urlservice pre-fetches resources and emits their urls
- the urlservice is the only component who knows which urls are valid
- i made some ES6 adaptions
- we keep the caching logic -> only regenerate xml if there is a change
- updated tests
- checked test coverage (100%)
### Re-work usage of Url utility
- replace all usages of `urlService.utils.urlFor` by `urlService.getByResourceId`
- only for resources e.g. post, author, tag
- this is important, because with dynamic routing we no longer create static urls based on the settings permalink on runtime
- adapt url utility
- adapt tests
2018-06-05 20:02:20 +03:00
|
|
|
'use strict';
|
2018-03-27 17:16:15 +03:00
|
|
|
// # Authors Helper
|
|
|
|
// Usage: `{{authors}}`, `{{authors separator=' - '}}`
|
|
|
|
//
|
|
|
|
// Returns a string of the authors on the post.
|
|
|
|
// By default, authors are separated by commas.
|
|
|
|
//
|
|
|
|
// Note that the standard {{#each authors}} implementation is unaffected by this helper.
|
2019-03-26 07:36:41 +03:00
|
|
|
const proxy = require('./proxy');
|
|
|
|
const _ = require('lodash');
|
|
|
|
const urlService = require('../services/url');
|
|
|
|
const {SafeString, templates, models} = proxy;
|
2018-03-27 17:16:15 +03:00
|
|
|
|
2019-03-26 07:36:41 +03:00
|
|
|
module.exports = function authors(options = {}) {
|
|
|
|
options.hash = options.hash || {};
|
✨Dynamic Routing Beta (#9596)
refs #9601
### Dynamic Routing
This is the beta version of dynamic routing.
- we had a initial implementation of "channels" available in the codebase
- we have removed and moved this implementation
- there is now a centralised place for dynamic routing - server/services/routing
- each routing component is represented by a router type e.g. collections, routes, static pages, taxonomies, rss, preview of posts
- keep as much as possible logic of routing helpers, middlewares and controllers
- ensure test coverage
- connect all the things together
- yaml file + validation
- routing + routers
- url service
- sitemaps
- url access
- deeper implementation of yaml validations
- e.g. hard require slashes
- ensure routing hierarchy/order
- e.g. you enable the subscriber app
- you have a custom static page, which lives under the same slug /subscribe
- static pages are stronger than apps
- e.g. the first collection owns the post it has filtered
- a post cannot live in two collections
- ensure apps are still working and hook into the routers layer (or better said: and register in the routing service)
- put as much as possible comments to the code base for better understanding
- ensure a clean debug log
- ensure we can unmount routes
- e.g. you have a collection permalink of /:slug/ represented by {globals.permalink}
- and you change the permalink in the admin to dated permalink
- the express route get's refreshed from /:slug/ to /:year/:month/:day/:slug/
- unmount without server restart, yey
- ensure we are backwards compatible
- e.g. render home.hbs for collection index if collection route is /
- ensure you can access your configured permalink from the settings table with {globals.permalink}
### Render 503 if url service did not finish
- return 503 if the url service has not finished generating the resource urls
### Rewrite sitemaps
- we have rewritten the sitemaps "service", because the url generator does no longer happen on runtime
- we generate all urls on bootstrap
- the sitemaps service will consume created resource and router urls
- these urls will be shown on the xml pages
- we listen on url events
- we listen on router events
- we no longer have to fetch the resources, which is nice
- the urlservice pre-fetches resources and emits their urls
- the urlservice is the only component who knows which urls are valid
- i made some ES6 adaptions
- we keep the caching logic -> only regenerate xml if there is a change
- updated tests
- checked test coverage (100%)
### Re-work usage of Url utility
- replace all usages of `urlService.utils.urlFor` by `urlService.getByResourceId`
- only for resources e.g. post, author, tag
- this is important, because with dynamic routing we no longer create static urls based on the settings permalink on runtime
- adapt url utility
- adapt tests
2018-06-05 20:02:20 +03:00
|
|
|
|
2019-03-26 07:36:41 +03:00
|
|
|
let {
|
|
|
|
autolink,
|
|
|
|
separator = ', ',
|
|
|
|
prefix = '',
|
|
|
|
suffix = '',
|
|
|
|
limit,
|
|
|
|
visibility,
|
|
|
|
from = 1,
|
|
|
|
to
|
|
|
|
} = options.hash;
|
|
|
|
let output = '';
|
|
|
|
const visibilityArr = models.Base.Model.parseVisibilityString(visibility);
|
|
|
|
|
|
|
|
autolink = !(_.isString(autolink) && autolink === 'false');
|
|
|
|
limit = limit ? parseInt(limit, 10) : limit;
|
|
|
|
from = from ? parseInt(from, 10) : from;
|
|
|
|
to = to ? parseInt(to, 10) : to;
|
2018-03-27 17:16:15 +03:00
|
|
|
|
|
|
|
function createAuthorsList(authors) {
|
|
|
|
function processAuthor(author) {
|
|
|
|
return autolink ? templates.link({
|
2018-06-12 18:36:58 +03:00
|
|
|
url: urlService.getUrlByResourceId(author.id, {withSubdirectory: true}),
|
2018-03-27 17:16:15 +03:00
|
|
|
text: _.escape(author.name)
|
|
|
|
}) : _.escape(author.name);
|
|
|
|
}
|
|
|
|
|
2019-03-26 07:36:41 +03:00
|
|
|
return models.Base.Model.filterByVisibility(authors, visibilityArr, !!visibility, processAuthor);
|
2018-03-27 17:16:15 +03:00
|
|
|
}
|
|
|
|
|
|
|
|
if (this.authors && this.authors.length) {
|
|
|
|
output = createAuthorsList(this.authors);
|
|
|
|
from -= 1; // From uses 1-indexed, but array uses 0-indexed.
|
|
|
|
to = to || limit + from || output.length;
|
|
|
|
output = output.slice(from, to).join(separator);
|
|
|
|
}
|
|
|
|
|
|
|
|
if (output) {
|
|
|
|
output = prefix + output + suffix;
|
|
|
|
}
|
|
|
|
|
|
|
|
return new SafeString(output);
|
|
|
|
};
|