Krzysztof Adamski

Meanwhile, I ended up using this workaround for tests. This stores current attribute in local variable and then sets it back after each execution of job. ``` current_attribute_value = Current.attribute...

You're totally right - I can see now where the problem was. So `app/assets/builds` directory didn't exist when RSpec was starting. And when framework starts Propshaft in `railtie.rb` is only...

I totally get you - yes, that should stay disabled. My question was rather about - not filtering out these directories that don't exist during initialisation phase.

Slightly different scenario 1. You start an app (I've pushed an example one: https://github.com/rience/propshaft_issue) 2. You open browser and open `http://localhost:3000` (so that Propshaft is initialisated) - you should see...

> Ah, ok. I get it. Since `builds` did not exist it was not added to the file watcher, so it does not matter how many times you refresh, the...

Shouldn't this rather part of Rails project template? All these solutions - `jsbundling`, `cssbundling-rails` and `dartsass-rails` are using `assets/builds` library in default configuration. So having this in one plane i.e....