Continuing from #13 , built on the models, and modular methods for database, collection and data and create an exportable WDBClient that ties the different steps (using the modular functions) and performs the action required.
Eg, to Add database, the wdbClient.AddDatabase(dbID) should
First check if DB with ID exists
Then (if db doesn't exist) call the databases.CreateDatabase() to create the db.
In this, there would be significant changes in the methods setup in #13 as we want to remove the steps baked into each other and also to remove dependancy on one function from another in same package (databases package methods needed to call the function check if exists of same package). Also the changes would be to just update/delete/get the data and not check existence.
[x] Update internal/* package methods
[x] Create methods on WDB Client tying in the different steps
Continuing from #13 , built on the models, and modular methods for database, collection and data and create an exportable
WDBClientthat ties the different steps (using the modular functions) and performs the action required.Eg, to Add database, the
wdbClient.AddDatabase(dbID)shoulddatabases.CreateDatabase()to create the db.In this, there would be significant changes in the methods setup in #13 as we want to remove the steps baked into each other and also to remove dependancy on one function from another in same package (databases package methods needed to call the function check if exists of same package). Also the changes would be to just update/delete/get the data and not check existence.
internal/*package methods