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

Allow to parameterize templates by ApplicationPath #48

Closed
intellifactory-bb opened this issue Dec 6, 2014 · 3 comments
Closed

Allow to parameterize templates by ApplicationPath #48

intellifactory-bb opened this issue Dec 6, 2014 · 3 comments

Comments

@intellifactory-bb
Copy link

In addition to the built-in "scripts" variable that expands to WebSharper resource imports, it would be helpful to have a "root" variable that would expand to the ApplicationPath. Such a variable would allow templates to work regardless of the deployment path, in both root and virtual-directory deployments. A common situation is the need to reference a CSS file, which could then be accomplished thus:

#!html
<link href="${root}/themes/site.css" rel="stylesheet" type="text/css" />

@intellifactory-bb
Copy link
Author

I would make this more general and allow placeholders (of type string) in attribute values. This way we wouldn't have to introduce another hard coded variable name.


Original comment by: Adam Granicz

@intellifactory-bb
Copy link
Author

But we already have them. ${ROOT} is exactly such a placeholder. It's user-definable (and re-definable).


Original comment by: Anton Tayanovskyy

@intellifactory-bb
Copy link
Author

Fix #48.

→ <<cset 39fe793b2f35>>


Original comment by: Anton Tayanovskyy

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant