swagger-api/swagger-codegen

[ERR!] GitHub API: GitHub rate limit reached.

Open

#6297 opened on Aug 12, 2017

View on GitHub
 (0 comments) (0 reactions) (0 assignees)HTML (12,701 stars) (5,474 forks)batch import
Client: TypeScriptEnhancement: Generalhelp wanted

Description

Description
> petstore-typescript-node-sample@1.0.0 postinstall /Users/travis/build/swagger-api/swagger-codegen/samples/client/petstore/typescript-angular
> tsd reinstall --overwrite
-> running reinstall

[ERR!] GitHub API: GitHub rate limit reached.
    To increase the limit use GitHub authentication.
    See: https://github.com/DefinitelyTyped/tsd#tsdrc

The issue was cause by typescript-angular petstore client still using tsd, which should be replaced by typings.

Swagger-codegen version

Latest master

Related issues/PRs

https://github.com/swagger-api/swagger-codegen/pull/6178

Suggest a fix/enhancement

Apply a fix similar to https://github.com/swagger-api/swagger-codegen/pull/6178

If anyone wants to work on this, please reply to let us know.

Contributor guide

Tech stack
typescriptangularnodejs
Domain
frontendapi
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
familiarity with TypeScriptnpm package management
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
85
Research direction
First, review the linked pull request #6178 to understand the fix pattern. Then, locate the `tsd.json` file in the samples/client/petstore/typescript angular directory and replace the `tsd` command with the `typings` equivalent. Ensure the `postinstall` script in `package.json` is updated accordingly. Test by running `npm install` to verify the rate limit issue is resolved.