especially because we can embed objects in other objects after the fact, the main thing we're missing will be access to being able to call the functions within the objects.
we have some potential issues w/ inheritence b/c tokens will expire and need to be redone for everyone
i guess we could have a google session class and then have the spreadsheets inherit from that. obviously sheets would inherit spreadsheets.
then we have to work out the calls - now we are instantiating them in effectively reverse order.

from 4d-google-workspace.

in this context, unlike merggoole, it seems like there isn't any point to trying to keep the sheets separate.
then again, there was a regex for getting a sheet id.

from 4d-google-workspace.

maybe another way to do this would be:

1. generate a comms object
2. sheet extends that object
3. sheet does its thing
4. parent (that owns comms and sheet) checks to see if comms expired and if so updates parent comms and any other child objects

from 4d-google-workspace.

passing a pointer to update comms might help

from 4d-google-workspace.

1. create comms object
2. create spreadsheet, passing pointer to comms
3. spreadsheet calls header function using pointer to comms data
4. if comms data is old, pointer is used to update comms data
   this gets us around not being able to use a pointer to the comms functions but having access to the comms data via a pointer.

from 4d-google-workspace.

Solution?

per vdl and KM conversation:

It seems that we should maybe do the following:

• comms - does the comms, doesn't really have any initialization, should probably be all functions
• auth - extends comms and does the auth and headers
• spreadsheets - extends comms and manages the spreadsheet data

since comms doesn't have any properties, by extending it we don't need to do anything else per se
We then pass the auth object to every spreadsheet object, and we can then refer to the auth properties because the object is a pointer.
The comms functions are automagically incorporated by reference, like a submodule, and thus we just call the functions
When we need auth, we just use the auth properties, which are incorporated.

from 4d-google-workspace.

v. 0.0.0.4
0b24a99

from 4d-google-workspace.