-
Notifications
You must be signed in to change notification settings - Fork 9
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
Update definition to include the .reflect
method, replaces .inspect
method
#10
Conversation
Notes on potential merge strategies:
|
LGTM 👍 |
I'd go with the second merge strategy. i.e. don't keep the buggy version in the registry. |
I have never maintained a typings library, so I want to be clear about your suggestion. Is your suggestion to have the registry file look something like:
With 2.X and 3.X being root directories of this repository? |
Kind of. Here's a real life example. {
"versions": {
"3.0.0": "github:typed-typings/npm-bluebird/3#COMMIT",
"2.0.0": "github:typed-typings/npm-bluebird/2#COMMIT"
}
} |
Do you want to remove |
Yes... I'll update the PR now. On Tue, Apr 26, 2016 at 9:51 AM, Louy Alakkad notifications@github.com
|
Awesome. Thank you. |
Looks like you are right -- it does return a Promise to a PromiseInspection. In regard to the comment, it is a holdover from the original definitions, which were written for the Bluebird 2.x If you want, feel free to go ahead and submit a PR -- otherwise I am working on another PR to fix some other differences from the Bluebird 2 -> 3 upgrade, and can roll it in there. |
If you don't mind it'd be cool if you could add those changes into your PR, since it's a very simple issue anyways. 😊 |
The
.inspect
method was removed by this commit, and had already been superseded by.reflect
.Bluebird API reference
Closes issue #9