Rasmus Kaj
Rasmus Kaj
Merged the example in #94 . The rendering traits can still be moved from the example to the feature, but that can wait for another PR.
I already did add a `tide013` feature, but that is minimal, it only provides the http-types `Mime` support through the `tide::http` reexport.
True. It could be fixed by adding a constant string before the name (so `foo.jpg` still becomes `foo_jpg` but `17.jpg` becomes `static_17_jpg`). Or it could just be a line in...
Yes, this seems like a defect in ructe. I'll try to fix it.
Hi! Thanks for this contribution! It seems like a good thing overall, I'll try to take good look at the details tomorrow (I'm a bit too tired today).
I don't think static file data has any big impact on compile times. The files has to be read at compile-time anyway to implement the hash in the file name...
Could be useful. But will the full path to the file be the same on the deployed server as in the build environment? Or would some kind of dist-dir parameter...
Yes, I fully agree about the goal. Unfortunately, I also agree that it is not as easy as it sounds. :-) I have considered way number 2, and I think...
Yes, some way of working as a macro has been in my long-term vision for ructe pretty much since the start. So It's nice to finally having an issue for...
After some experimentation, I have more or less decided against the solution I suggsted in #29, and in favor of something like https://github.com/kaj/ructe/pull/42#issuecomment-510231217 . That would hopefully make it possilble...