I love the functionality of 3T, but inserting a JSON with Integers in it is potentially dangerous. We have an application that instantly grabs new documents and it can't cope with floats. But all numbers in a JSON are converted to float unless they are explicitely marked as Integer. I know that this request is not new and that the problem originates in JavaScript (found case from 2014). Maybe something can be changed now that 6 years have passed.