In your docs it should be mentionded that if you are using a existing mongodb connection which is being instantiated when you configure your app it can happen that your services are not going to use the mixin of the adapters. Take a look at this code snippet:
feathers-sync gets the mongoClient when the connection to mongodb has been established but the services have already been configured and added to the router. This can lead to unexpected behaviour when you expect your services to be extended by the mongo adapter mixin.
In your docs it should be mentionded that if you are using a existing mongodb connection which is being instantiated when you configure your app it can happen that your services are not going to use the mixin of the adapters. Take a look at this code snippet:
feathers-sync gets the mongoClient when the connection to mongodb has been established but the services have already been configured and added to the router. This can lead to unexpected behaviour when you expect your services to be extended by the mongo adapter mixin.