I think somewhat proposed this before and I thought it always made more sense to support just setting the "compiled" option in views.php to null rather than inventing a new configuration option.

And just make an is_null check against sourcePath inside the isExpired method? Would need a change in the compile method as well I suspect.

You'd still need to compile the template, you just want the cache to always present as expired, right?

Already refs #12586 and #12587, and maybe there was another topic about this.

You're right @acasar. I did a little more digging based on Taylor's suggestion; setting the compiled option to null has some deeper reaching side effects, given that the view's render method still tries to load the cached contents from disk.

I'll do some more work on this this weekend.

I've done a little more digging; it seems that with a fresh 5.2 install if you set view.compiled to null as implemented in #12586, you'll wind up with an exception (which the unit tests don't pick up).

Subsequent commits here should address both that bug, as well as changes discussed in this PR. It doesn't appear as simple as testing for null, though, as you still need to compile the blade template at some point, which is the point of the cached file.

Maybe cachePath could be looked for "falsy" rather than just "null"?

Based on the above, I think that having a new config option may still be worthwhile, given the compiler engine requires including the compiled blade via path (and not passing a compiled string around). By the time execution gets to the engine, it has no knowledge of the compiled path being null or otherwise.

Not sure I'm going to end up adding this. There are already so many ways you could do it, such as a global middleware that checks env and runs view:clear or something.

Thanks @taylorotwell - I agree, there's a few other approaches to this. Although on further inspection, there shouldn't even theoretically be a (server-side) caching issues anyway, given the way expirations are handled internally.

@taylorotwell Just setting view.compiled to null causes in a fatal error. Is there another way? Disabling the Blade cache on read-only system like Heroku is essential.