Rational for adding collection wide typings

README.md

Having to add typings to each require is almost as useless as not having typings at all. For example,

import DB from "nedb"
const myCollection = new nedb(DB)
// insert one kind of document
myCollection.insert<{name:string}>({name:"nedb"})
// expect to find a different kind of document
myCollection.findOne<{name:number}>({},(err,doc) => console.log(typeof doc.name))

This is especially true when the a collection is exported or passed to another module.

import DB from "nedb"
const myCollection = new nedb(DB)
// insert one kind of document
myCollection.insert({name:"nedb"})
// now expecting to find a different kind of document raises an error
myCollection.findOne<{name:number}>({},(err,doc) => console.log(typeof doc.name))