No intent to fix the underlying issue as of now, but a warning should at least be added in the documentation.
You must be logged in to leave a comment.