Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Do not rename .gs files to .js before pushing

See original GitHub issue

Expected Behavior

When using : clasp push a file named: Code.gs is still named Code.gs (locally, i’m not talking about remote)

Actual Behavior

When using : clasp push a file named: Code.gs is renamed to Code.js

The project files should not be changed by the pushing operation. Any preparation to the push operation should be done by the tool, without affecting project files.

Steps to Reproduce the Problem

use clasp push with *.gs files

Specifications

Version (npm list | grep clasp): 1.1.5
OS (Mac/Linux/Windows): all ?

Issue Analytics

State:
Created 6 years ago
Comments:18 (15 by maintainers)

Top GitHub Comments

5reactions

JeanRemiDelteilcommented, Jun 19, 2018

much appreciated 👍 I suppose we can close this issue now ?

fixed by #27

4reactions

erickoledadevrelcommented, Apr 9, 2018

+1 to this issue, clasp shouldn’t rename files. The clasp push command should be a read-only operation in regards to the file system.

I’d rather see:

clasp push supports both .js and .gs extensions, but outputs a warning for .gs files noting the preference for .js
clasp pull always creates .js files, regardless of whether or not .gs files are present