Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expose enableEmoji as a site variable #9902

Closed
rootwork opened this issue May 16, 2022 · 2 comments
Closed

Expose enableEmoji as a site variable #9902

rootwork opened this issue May 16, 2022 · 2 comments

Comments

@rootwork
Copy link

rootwork commented May 16, 2022

From #7170:

Hugo themes determine what text gets emojified for us and what doesn't. Hugo already helps to emojify content if enableEmoji is set to true. In order to give the greatest flexibility and control enableEmoji should be exposed as a site variables (i.e. .Site.EnableEmoji).

This would allow themes to conditionally run text (like titles) through emojify if enableEmoji is set; currently there's no way to do this and respect the site config.

(Since the Hugo repo aggressively closes proposals that have no activity on them, the only way I could add my "+1" to the #7170 proposal was to create a new issue.)

@bep
Copy link
Member

bep commented May 25, 2022

No, we're not doing this. I have written about this before, but we're very restrictive about making the site configuration part of the API, as it usually restricts future changes in some unknown way.

@bep bep closed this as completed May 25, 2022
@github-actions
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 16, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants