You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
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:
The text was updated successfully, but these errors were encountered: