#`--workdir` removal
1 messages · Page 1 of 1 (latest)
Yeah, that's true, it's potentially breaking.
What's the reason we're looking at removing it? Sorry, I remember discussing, but now struggle to remember the context.
Is it because we wanted to use the --workdir opt for something else maybe?
Yes, for dagger shell.
I wonder if I can move the current global flag into session. Not sure if people use it in dagger run too.
yeah, i think that sounds okay to me
i'm not sure why we need it on dagger run actually - you should just be able to go to the right directory first?
it's only for auto-provisioning where i guess it makes some sense
Yeah, I suppose.
Can it impact the loading of the module for client generation?
I'm not sure since I'm using the findup logic (that is now inside the engine) but just to double check
really doubt it 🤔 are you using Workdir as an option anywhere in the client gen?