You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It might be useful sometimes to use the write API in a no-op way. This is quite functional programming-ish and would align well with our job code - you can safely pass no data into appendValues and it'll happily do nothing. This saves us an if statement.
If the values to appendValues or batchUpdateValues are nullish or empty, we should not call out the google API and return early. Maybe we should log a message saying skipping appendValues as no data passed or something.
Hi @PiusKariuki - maybe you could take a look at this one?
Is the issue is clear? The problem is (I think) that if you try and do appendValues() but pass an empty array (or maybe an undefined/null value), you'll get an error.
This means that users have to do fnIf() now to maybe send data to sheets, but this is needlessly awkward.
It might be useful sometimes to use the write API in a no-op way. This is quite functional programming-ish and would align well with our job code - you can safely pass no data into
appendValues
and it'll happily do nothing. This saves us an if statement.If the values to
appendValues
orbatchUpdateValues
are nullish or empty, we should not call out the google API and return early. Maybe we should log a message sayingskipping appendValues as no data passed
or something.Example job:
The text was updated successfully, but these errors were encountered: