Response to a ticket submitted by one of my colleagues:
Currently there is no workaround for this issue but to remove the warning our R&D team will release a patch in rich text version 2.3.0. Tentative ETA is by tomorrow (Feb 9).
New version has been released