Oh sorry, I think I misunderstood the issue. I assumed this was an issue that was present in 2.2.0 that had been fixed in 2.2.1 and the fix had not been merged to master yet.
Oh sorry, I think I misunderstood the issue. I assumed this was an issue that was present in 2.2.0 that had been fixed in 2.2.1 and the fix had not been merged to master yet.