Fix clasp login

[campionfellin]

Now it checks for local rc file before logging in.

Previously, if you ran clasp login --ownkey followed by clasp login you would have 2 .clasprc.json files, on in your homedir and one in your working directory. Now, it checks for a local rc file first.

Signed-off-by: campionfellin campionfellin@gmail.com

Works on #131 (note, that we may have to implement some sort of check before every command so they do not always default to the rc file in your homedir.)

• npm run test succeeds. (no tests for login yet)
• npm run lint succeeds.
• Appropriate changes to README are included in PR.

[coveralls]

Pull Request Test Coverage Report for Build 155

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 216 unchanged lines in 1 file lost coverage.
• Overall coverage decreased (-0.06%) to 14.024%

---

Files with Coverage Reduction	New Missed Lines	%
index.js	216	6.55%

Totals
Change from base Build 154:	-0.06%
Covered Lines:	159
Relevant Lines:	864

---

💛 - Coveralls

[grant]

Is this ready?

[campionfellin]

I would say this part is. This prevents you from logging in using simply clasp login when you already have a .clasprc.json in your working directory.

The next step (whether this is a separate PR or on this PR) is to change the behavior of getProjectSettings

clasp/src/utils.ts

Line 154 in 0080f67

export function getProjectSettings(failSilently?: boolean): Promise<ProjectSettings> {

It should check the current directory first for .clasprc.json and if not found then check the homedir.

Once this is done, commands like clasp list, etc should work after using clasp login --ownkey.
Do you think that should be with this or separate?

[grant]

Thanks for the small PR. Small separate changes are good.