If you actually read through, the option to disable the functionality was already present… just not documented. So it seems the documentation repo was the correct place to open it
replyYep, that reply was posted after my comment here, so it turns out the documentation really was the right place for the issue.
reply