Here is the version for those of you who can use a new version of C#: // add $ at start to mark string as template var template = $”Your job finished at {FinishTime} and your file is available for download at {FileURL}.” In a line – this is now a fully supported language feature … Read more
Handlebars partials take a second parameter which becomes the context for the partial: {{> person this}} In versions v2.0.0 alpha and later, you can also pass a hash of named parameters: {{> person headline=”Headline”}} You can see the tests for these scenarios: https://github.com/wycats/handlebars.js/blob/ce74c36118ffed1779889d97e6a2a1028ae61510/spec/qunit_spec.js#L456-L462 https://github.com/wycats/handlebars.js/blob/e290ec24f131f89ddf2c6aeb707a4884d41c3c6d/spec/partials.js#L26-L32
This should work fine: {{ ‘http://’ ~ app.request.host }} To add a filter – like ‘trans’ – in the same tag use {{ (‘http://’ ~ app.request.host) | trans }} As Adam Elsodaney points out, you can also use string interpolation, this does require double quoted strings: {{ “http://#{app.request.host}” }}
Update Here is a solution from yottatsa on a similar question that only does replacement for variables like $VAR or ${VAR}, and is a brief one-liner i=32 word=foo envsubst < template.txt Of course if i and word are in your environment, then it is just envsubst < template.txt On my Mac it looks like it … Read more
There are two issues here: Yes, you can run the Razor View Engine outside of the context of an ASP.NET app domain, as explained in Andrew’s blog: http://vibrantcode.com/blog/2010/11/16/hosting-razor-outside-of-aspnet-revised-for-mvc3-rc.html However, Razor is still primarily focused on generating xml-like markup (e.g. HTML) in the sense that the Razor parser uses the presence of <tags> to determine the … Read more
Try envsubst FOO=foo BAR=bar export FOO BAR envsubst <<EOF FOO is $FOO BAR is $BAR EOF
Technically, it doesn’t matter where you declare the <f:metadata> in the view as long as it’s in the top level view (so, when using templating, in the template client and thus not in the master template). When the view get built, the metadata is basically not part of the JSF component tree, but of the … Read more
Introduction The proper JSF 2.x way is using <h:outputStylesheet>, <h:outputScript> and <h:graphicImage> with a name referring the path relative to webapp’s /resources folder. This way you don’t need to worry about the context path as you would do in JSF 1.x. See also How to include CSS relative to context path in JSF 1.x? Folder … Read more