These methods will allow you to get or set the database you want to use.

I think it makes more sense to use client() method instead of get(). I want to depreciate get() and use client() instead to get the Mongo client.

I want to support replica sets and sharded clusters. I wouldn't be hard to configure this as it only requires editing the createUri() method and a few changes to the config file.

Most of the time you will not be switching databases often, so defining a default database to use would make this much easier to use.

Of course we still need to be able to override this value if a user is using the non-default database.

My thoughts are to create a setting in config/mongo.php which is default_database and that will be set on the __construct() method as the assumed database to use unless set.

This is a HUGE project i know, but it is worth it if I can find the time to do it. Maybe its best as a seperate package, so that those that simply want the wrapper can get that, but the second package (such as devmarketer/laramongo-auth) would inherit/require this package and add functionality on top of it.

I need to investigate more about what this would entail. The Laravel Auth is very fragmented and involves injecting into a lot of different methods and functions.

I copied this file structure over from my EasyNav package and forgot to change the content inside of the contibuting.md file so it doesn't reference the EasyNav package, but instead references the LaraMongo package.

We should create a page that explains how to fix this.