Custom file extension on `clasp pull`
See original GitHub issueExpected Behavior
Right now clasp pull
defaults Apps Script files to .js
.
A user should be able to specify which file extension should be used when pulling new files.
Solution: Add a new property to .clasp.json
:
{
'fileExtension': 'gs'
}
Other values could be 'js'
or 'ts'
(or anything else).
Actual Behavior
All pulled files have .js
.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:2
- Comments:7 (5 by maintainers)
Top Results From Across the Web
How do I create and push new files client side?
According to the docs (github.com/google/clasp#push) they should get pushed just fine, provided they are the correct type. You don't mention the ...
Read more >Command Line Interface using clasp | Apps Script
This command uploads all of a script project's files from your computer to Google Drive. clasp push. List project versions.
Read more >How to Write Google Apps Script Code Locally in VS ...
clasp login; clasp clone; clasp push -w; clasp pull. clasp login allows you to save ... Save the file and type clasp push...
Read more >Extensions How to Handle Custom File Formats
Many modern file formats already come in XML format which allows to extract information with any XML conforming parser, e.g., as implemented in...
Read more >Google Apps Script to Visual Studio Code with Clasp
clasp is a command-line tool that allows you to connect with your Google Apps Script files to: Pull them from the cloud. Push...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This should have been added in one of the recent versions of clasp.
@sat0yu created #304 which should fix this. I will close this issue when clasp is published on npm (probably next week).