Adding support for specifying QuickBooks Model and more...

[TeknoloGenie]

Current structure dynamically created the model once the requested model is sent through the queueTransaction method which are coming from the reSync method. So currently if someone wanted to ONLY use the Customer data from QuickBooks they would be fish in the water.

This project was created to accomplish a goal for a clients project we had, as of now (the time of this post) its strictly setup for gathering the required data our client needed. Its time to support the needs of the developers now instead of the client.

So to start this issue will be my first matter of business, refactoring the current structure and logic of the connector to enable the ability to define what QuickBooks data they want, by creating the model within their loopback project and extending the built in models provided by this connector.

Heres a step by step guide of what it might look like from start to finish if a developer wants to get ONLY Customer's, someone please feel free to step in with any suggestions.

1. run npm install loopback-connector-quickbooks
2. setup the connector inside the datasource.json
3. create the Customer LoopbackJS Model, and set its base Model as QBCustomer
4. extend upon the Model as needed....

[TeknoloGenie]

Creating new issue #8 and #9 to help divide this work up. Will close once both those are completed