Can’t you purify it on render instead (using DOMPurify or another lib to process the field before sending it to dangerouslySetInnerHTML)?
Sometimes we need to inject scripts into HTML fields (third-party embeds and such) and I would hate to have Dato scrub it without asking. If it’s an option that can be set on a per-field basis, that’s fine I suppose. But then you’d still have to figure out what tags/props to allow and eventually you’d just recreate the entire complexity of DOMPurify configuration anyhow. Might this be a job better handled on the frontend than the database?