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
Optional debug logging would go a long way in figuring out what is going on in the clasp API when things do not work as expected. A very common practice in the node community is to utilize debug. If you want to gain lazy logging please have a look at debug-fabulous (shameless plug).
Expected Behavior
export DEBUG="@google/clasp*"
@google/clasp:getProjectSettings oh hi I am a debug statement
Clasp has been split into multiple files with a testing framework that tests individual utility methods.
I don't know exactly what debug logging this issue would like to see, but I don't think contributors would need a DEBUG setting to make debugging clasp easier. Better testing is preferred over better logging.
I'll close this issue, but feel free to create a new one when there's something specific that should be added to clasp.
Optional debug logging would go a long way in figuring out what is going on in the clasp API when things do not work as expected. A very common practice in the node community is to utilize debug. If you want to gain lazy logging please have a look at debug-fabulous (shameless plug).
Expected Behavior
export DEBUG="@google/clasp*"
@google/clasp:getProjectSettings oh hi I am a debug statement
To turn on useful optional log messages.
Actual Behavior
Only errors are logged.
Examples
https://github.com/gulp-sourcemaps/gulp-sourcemaps/blob/master/src/debug.js#L1
https://github.com/gulp-sourcemaps/gulp-sourcemaps/blob/master/src/init/index.js#L49
The text was updated successfully, but these errors were encountered: