fd20f90cca
- The original intention of the proxy was to collect up all the requires in our helpers into one place - This has since been expanded and used in more places, in more ways - In hindsight there are now multiple different types of requires in the proxy: - One: true frontend rendering framework requires (stuff from deep inside theme-engine) - Two: data manipulation/sdk stuff, belongs to the frontend, ways to process API data - Three: actual core stuff from Ghost, that we wish wasn't here / needs to be passed in a controlled way - This commit pulls out One into a new rendering service, so at least that stuff is managed independently - This draws the lines clearly between what's internal to the frontend and what isn't - It also highlights that the theme-engine needs to be divided up / refactored so that we don't have these deep requires
21 lines
628 B
JavaScript
21 lines
628 B
JavaScript
// # Facebook URL Helper
|
|
// Usage: `{{facebook_url}}` or `{{facebook_url author.facebook}}`
|
|
//
|
|
// Output a url for a facebook username
|
|
const {socialUrls} = require('../services/proxy');
|
|
const {localUtils} = require('../services/rendering');
|
|
|
|
// We use the name facebook_url to match the helper for consistency:
|
|
module.exports = function facebook_url(username, options) { // eslint-disable-line camelcase
|
|
if (!options) {
|
|
options = username;
|
|
username = localUtils.findKey('facebook', this, options.data.site);
|
|
}
|
|
|
|
if (username) {
|
|
return socialUrls.facebook(username);
|
|
}
|
|
|
|
return null;
|
|
};
|