and it would be called just once
I basically want a way of having complete isolation wrt deps
I dunno, I had the same feeling initially, but now if kinda feels right
needs further thinking I suppose
I just think it's better to require everything eagerly during setup
when booting, YES OF COURSE
when loading a test, NO OF COURSE NOT
ie
rspec spec/unit/foo_spec.rb should run in complete isolation
wrt deps
atm I require spec-helper which loads the app, this is nonsense
when I see “123421.214412341 seconds to load files” in the rspec output, I cry
Fair point
If you load in isolation, how do you know the method under test hasn't been monkey wrenched though?
lol
Monkey patched
or scary, not sure
It's funny because it's true
I can now see what changes are needed to achieve isolation
I need to separate container configuration from finalization
it was collapsed into one thing, it is a mistake
which should be trivial
pretty much looping through names, asking container if it exists, if not, gsubbing dots with slashes, asking container to require missing stuff
I want to require the container in the spec helper and it should have the config in place, bkz config is a dependency too for stuff like db url etc
then the import stuff should be able to take care of everything
ultimate goal is to be able to run tests in complete isolation
so you don’t load tons of files w/o any good reason
I will call this feature “Summer"
becauase summer comes after spring
can we have
include Dry::Constructor(:foo, :bar, kwargs: true) too? :D
although I gotta say my use-case is pretty test-specific
so ie I want to do
Something.new(foo: double) and don’t care about the rest
with positioned args it is weird, I gotta pass nils
nils are replaced by auto-inject