Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

document how to configure clasp dev environment #3

Open
allenday opened this issue Aug 18, 2020 · 5 comments
Open

document how to configure clasp dev environment #3

allenday opened this issue Aug 18, 2020 · 5 comments
Assignees
Labels
bug Something isn't working

Comments

@allenday
Copy link
Member

$ npm run push

> @ push /Users/allenday/src/google/data-studio-connectors/crypto-analytics
> dscc-scripts connector push_changes


No valid .clasp.json project file. You may need to `create` or `clone` a project first.
Command failed: npx @google/clasp push
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @ push: `dscc-scripts connector push_changes`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the @ push script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
@allenday allenday added the bug Something isn't working label Aug 18, 2020
@allenday
Copy link
Member Author

I updated the README with a link for how to init the .clasp.json file, but I'm not sure if this solves the problem, as npm run try_latest still fails.

It is not clear where the connectorId is defined. See attached screenshot:

Screen Shot 2020-08-18 at 2 17 27 PM

@allenday allenday changed the title npm push fails - missing .clasp.json file need to define steps in README for configuring clasp dev environment Aug 18, 2020
@allenday allenday changed the title need to define steps in README for configuring clasp dev environment document how to configure clasp dev environment Aug 18, 2020
@franckc
Copy link

franckc commented Aug 19, 2020

Ah sorry, my bad for not adding more details.

Following these steps should fix the issue:
https://developers.google.com/datastudio/connector/local-development

I'll try on a fresh git clone to make sure it works and will update the README accordingly.

@allenday
Copy link
Member Author

allenday commented Aug 19, 2020

thanks - this is still not enough detail and I'm thrashing trying to get it to integrate. not clear do I need to pre-create the project and copy scriptId in, or if I should create fresh with dscc-gen.

@allenday
Copy link
Member Author

I'll stop work now. FYI the readme should be considered inaccurate and needs to be QAed, my edits are not correctly setting up the env, I keep getting stuck on this scriptId issue on npm try try_latest

@franckc
Copy link

franckc commented Aug 20, 2020

Got it. Yep, let me clean this up. Will ping this thread once I've had a chance to try the whole setup from fresh...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants