Closed LordRatte closed 11 months ago
699, #696, #691, #690 are all the same. I suggest someone look into this comment and push their PR forward with a solution.
What do you mean "Push their solution forward"? Is that a process on this project or a new git thing etc.?
@LordRatte I just mean that there are several PRs that claim to make the exact same fix, but I think that my comment should be addressed. If someone does that (i.e. put in a bit more work), maybe their PR will be chosen as the fix, or at least a starting point.
(I'm just another random person and cannot merge any PRs; just making a suggestion in how to get things ready for merging.)
thanks for contribution. This has been fixed in pull-request #696, so we will close this one 🙏 We will release a new version within a few days.