Ghost/core/frontend/helpers/link_class.js
Hannah Wolfe 59b9f161dd Moved non-helper code out of helpers
- the helper dir also contained some code used with helpers - utils and helper-helpers?
- the goal here was for helpers to be the only thing in their folder so we can look at moving them out
- all other code has been moved to services/themes for now, which is not the right place either
- services/themes is a catch-all for theme storage, loading, validation, rendering and more, needs to be broken down
2020-04-10 12:27:43 +01:00

30 lines
1.2 KiB
JavaScript

// # link_class helper
const _ = require('lodash');
const {config, SafeString, errors, i18n, localUtils} = require('../services/proxy');
const {buildLinkClasses} = localUtils;
module.exports = function link_class(options) { // eslint-disable-line camelcase
options = options || {};
options.hash = options.hash || {};
options.data = options.data || {};
// If there is no for provided, this is theme dev error, so we throw an error to make this clear.
if (!_.has(options.hash, 'for')) {
throw new errors.IncorrectUsageError({
message: i18n.t('warnings.helpers.link_class.forIsRequired')
});
}
// If the for attribute is present but empty, this is probably a dynamic data problem, hard for theme devs to track down
// E.g. {{link_class for=slug}} in a context where slug returns an empty string
// Error's here aren't useful (same as with empty get helper filters) so we fallback gracefully
if (!options.hash.for) {
options.hash.for = '';
}
let href = options.hash.for.string || options.hash.for;
let classes = buildLinkClasses(config.get('url'), href, options);
return new SafeString(classes.join(' '));
};