Jan Nedbal
Jan Nedbal
Are you going to implement this feature?
Commit e4abdef49f2c12e84e3eff3a06a574fd6150f3b5 caused this, any chance this will be reverted? Should I send PR?
@Tharos Develop branch is now merged in stable, did you miss this issue?
@castamir So this behaviour has changed in 3.0 and will not be reverted in future releases of 3.x (but there should be big warning about this BC break in release...
Thank you, now I see the huge complexity you were dealing when implementing this. Good work! Anyway, shouldnt you be able to detect all those settings from EM when provided...
> Maybe we could add a config parameter for this. I think that would be beneficial.
> it makes the resulting code more portable That might be super important for libraries, but not for company codebase, where you use single driver and single setup. So as...
@ondrejmirtes Any reference to a fix?
That fixes the issue, but it is pretty unclear from the error message. Hopefully people find this thread then...
I was hoping you tell me just remove that nonsense condition here :) I can create also an issue if you want, so should I?