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
Ultimately we we would like to use the layout and layoutPath in vision.
We have some problems though:
Our engine calls Riot.render which is ideally what we want (can write layout just as another tag) but at the same time strips out all scripts and style elements which may be useful.
Even avoiding that, the result of the engine doesn't produce valid html (not sure why, may be easy to solve..)
Can't find away to distinguish when loading a layout tag or a view tag since not all the options are passed down, hence can't correct any of above nor can we only append scripts to view tags
As a result an initial solution is to let them give us a full html file which is static bar the injecting of content at the placeholder <<<RIOT>>>. They can have it as a layout by setting layout and layoutPath in the compileOptions with default layout.html just like the other way.
When we find a way to deal with above problems, I'd be very happy to revert but for now this approach works for what we want and so long as enough warning is given should be easy to use.
The text was updated successfully, but these errors were encountered:
+ Create layout feature to have foundation html to be inject with riot content.
+ Cache this process
+ Update existing cacheing to make slightly more efficient
+ Update examples to use layout feature
Related: #16, #19, #20
Ultimately we we would like to use the
layout
andlayoutPath
in vision.We have some problems though:
As a result an initial solution is to let them give us a full html file which is static bar the injecting of content at the placeholder
<<<RIOT>>>
. They can have it as a layout by settinglayout
andlayoutPath
in thecompileOptions
with defaultlayout.html
just like the other way.When we find a way to deal with above problems, I'd be very happy to revert but for now this approach works for what we want and so long as enough warning is given should be easy to use.
The text was updated successfully, but these errors were encountered: