Open laur89 opened 1 year ago
Ye this is going to need quite a bit of research/know-how. Would you be willing to merge this as-is, considering it's reportedly solved problem to one user. And possibly/hopefully it improves existing logic somewhat.
Ye this is going to need quite a bit of research/know-how. Would you be willing to merge this as-is, considering it's reportedly solved problem to one user. And possibly/hopefully it improves existing logic somewhat.
Two users. :-) I have been waiting for this merge, and updated Docker image, since the opening of this PR.
Hello there, i've not forgotten about you.
But i'm lacking time to review that. I try to give it a look ASAP
Do you have any idea if and when you'll have the time to look at this, @anthonyraymond? I don't want to rush you, I'm already very grateful for what you did with this project so far, I'm just looking for an ETA.
Hello, i'm still unsure if i want to merge this as-is or not. Not sure if that makes its more unsafe or not.
An analogy for this PR is:
That is a valid point. Would it be possible to make it optional in config? @laur89 @anthonyraymond
@anthonyraymond i think it's best to just add a toggle in settings. for me it works great but maybe others can have issues, indeed. can't wait to see this merged and published <3
I don't think the config option will come anytime soon either, right? 😔
@anthonyraymond can we please merge this as well? been using it since then and it's all good. maybe add a config toggle in the settings just in case?
@rursache i don't think this is ever going to be added as is. It's sounds a bit dangerous for most people.
I'll include a real and complete implementation in the next version (built from scratch), but for now i prefer not to include it as is
@anthonyraymond I'll include a real and complete implementation in the next version (built from scratch), but for now i prefer not to include it as is
thank you, looking forward to your implementation!
~Note this change is on top of #172 -- merge that beforehand.~ merged