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
I'm not sure what the current suggested way to update your own apps script project is (perhaps running uninstall on the current project, copying a new project, adding back customizations and then running install... or maybe just copying and pasting files?). I think maybe there should be a spot in the comments or README that specifies this. I don't mind making a PR to that effect.
However, in general I think it's easier to easier to pull down new releases/changes from github and push them to Google apps script with the clasp CLI. One of the issues with this right now is that when you pull down changes from a google apps script project it renames files with a .gs extension to use .js locally (and therefore creates a duplicate of each file with a different extension). So I was wondering if it might make sense to rename .gs files with the .js extension in this repo.
Another thing to make updates a bit cleaner would be to separate out the config section into its own file.
... So 3 proposed changes:
Add update instructions (assuming they're not already somewhere)
Rename .gs files to use .js
Externalize personal config to a config.js or config.json file
The text was updated successfully, but these errors were encountered:
The issue where claps push renames files clasp issue #51 has now been fixed. As of 2.4.2 the behaviour is definitely to leave the .gs extension when pushing local files into script files.
Only 1. and 3. would be required.
Thanks for including those, I reckon they should be clear enough for anyone who is advanced enough to want to try clasp.
Thanks also for your efforts to rationalise and improve the project structure, I hope that the community gets the hang of it quickly, as it looks more logical to me - well done
I'm not sure what the current suggested way to update your own apps script project is (perhaps running uninstall on the current project, copying a new project, adding back customizations and then running install... or maybe just copying and pasting files?). I think maybe there should be a spot in the comments or README that specifies this. I don't mind making a PR to that effect.
However, in general I think it's easier to easier to pull down new releases/changes from github and push them to Google apps script with the clasp CLI. One of the issues with this right now is that when you pull down changes from a google apps script project it renames files with a .gs extension to use .js locally (and therefore creates a duplicate of each file with a different extension). So I was wondering if it might make sense to rename .gs files with the .js extension in this repo.
Another thing to make updates a bit cleaner would be to separate out the config section into its own file.
... So 3 proposed changes:
The text was updated successfully, but these errors were encountered: