Add variable expansion support in shortcode params

[bep]

See 3) in twbs/bootstrap#24475 (comment)

Not sure how this would look like, but something ala Bash's variable expansion, eg.

{{< relref "${.Site.Params.version}/features" >}}

[moorereason]

Can’t this already be solved by a simple wrapper shortcode? “vref” and “vrelref” for example.

[bep]

Can’t this already be solved by a simple wrapper shortcode?

Yes. But it is a fairly common problem, and you it would potentially create lots of "wrapper variants" and make the content "unportable".

I don't think I'm solving this unless I can find a simple and fast way to do it -- but there are obvious and useful use cases for this.

[jicksta]

I think I've been running into a similar issue.

https://github.com/jicksta/repro-hugo-lexer-issue

I'm trying to render a Hugo page from a data file that passes dynamic data into a shortcode as a parameter. Doing something like:

{{< myshortcode $somethingdynamic >}}

actually generates a lexer error at the "$" (or at the . in the case of .somethingdynamic).

Maybe I'm missing something idiomatic about Go / Hugo templating, but shouldn't dynamic data be a supported use-case for shortcodes?

More info can be found in the README of the repo linked above.

Thanks btw for all the great work on Hugo so far!

[stale]

This issue has been automatically marked as stale because it has not had recent activity. The resources of the Hugo team are limited, and so we are asking for your help.
If this is a bug and you can still reproduce this error on the master branch, please reply with all of the information you have about it in order to keep the issue open.
If this is a feature request, and you feel that it is still relevant and valuable, please tell us why.
This issue will automatically be closed in the near future if no further activity occurs. Thank you for all your contributions.

[XhmikosR]

This is still a valid request.

[github-actions]

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.