Yes, you are right about the static file delivery. What you can also do, is to put all your static files inside a specifc directory, for instance static/, then you just need to check if the request is for some file under that directory and closeAndRedispatch.

Ok, I see – that does of course make perfect sense. Looking forward to your next release! Do you have, or are you going to have, a sentraliced place for all Opera-libraries? (I can’t seem to find any as of now)

Regarding the _request event handler:
That’s something to keep in mind.

Let’s now say I want to dispatch to the static content as long as there exists a matching file, and otherwise call “_request”-event – I had to create a function which used fileio and try to open the file, catch any errors, and then call closeAndRedispatch() only if successfully open. I’ve read through the documentation but can’t seem to find any sleeker way – what do you think?

Regarding the import-bug:
Great! I really appreciate the quick feedback and follow-up.

“will there be any side-effects as you know by switching?”
Depends on your code actually… this way if you have a data-list each {{}} inside it will be intact and only parsed by the parseDataAttributes function (but I would say that in normal conditions you won’t get any problem).
I will change this in the future so you don’t have to worry about that (right now the fillValues is getting -all- {{}} elements, doesn’t stop at a data-list for instance)

Regarding arve’s comment about the _request event handler, keep in mind that after listening to this event static files -won’t- be served automatically anymore, you’ll have to explicitly response.closeAndRedispatch() for that to happen.

PS: already fixed the “Imported files through the templater can’t be empty” in our internal version, you can patch this by adding “if( !nodes ) { return; }” before the “if ( nodes.length )” on the importTemplate function.

That’s a good tip indeed – I didn’t think of that kind of use for it (just CSS and JS etc). As far as I can see this apply to the public_html-folder. Anywhere else? I did a quick test with the fileio but I assume it’s only through the app-specific JS you can work with that – right?

Thanks!

Thanks for your comment. Ah, I see – I hadn’t tested using variables in standard attributes which, turned out, worked great as it was.
Thanks for the tip which worked perfectly.

Is there any reasons to keep the order as it was originally – read: will there be any side-effects as you know by switching?

“The templater doesn’t currently seem to allow variables in attributes”:
The “patch” you’re looking for is switching this.fillValues(data) with this.parseDataAttributes(data) on the this.parse(data) function, which will make the variables being parsed before all those data attributes.

“Imported files through the templater can’t be empty”
This, however, is a bug.

Additionally, there is a catch-all request handler you can listen to, ‘_request’, which is dispatched after the more specific request.