-
-
Notifications
You must be signed in to change notification settings - Fork 7
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
TypeScript support #6
Comments
I don't mind a typings file in this project, as the API will likely remain stable for the time being. A |
Would you better like a |
The former: |
Motivation ---------- This will add types. The behaviour has changed minimally. The conditions don't check for `key in data` but simply `data.key`. I think considering the differences, it's perfectly for fine for this library. How to test ----------- 1. `npm run build` 2. Have a look in `dist/` close derhuerst#6
Motivation ---------- This will add types. The behaviour has changed minimally. The conditions don't check for `key in data` but simply `data.key`. I think considering the differences, it's perfectly for fine for this library. How to test ----------- 1. `npm run build` 2. Have a look in `dist/` close derhuerst#6
Motivation ---------- This will add types. The behaviour has changed minimally. The conditions don't check for `key in data` but simply `data.key`. I think considering the differences, it's perfectly for fine for this library. How to test ----------- 1. `npm run build` 2. Have a look in `dist/` close derhuerst#6
Motivation ---------- This will add types. The behaviour has changed minimally. The conditions don't check for `key in data` but simply `data.key`. I think considering the differences, it's perfectly for fine for this library. How to test ----------- 1. `npm run build` 2. Have a look in `dist/` close derhuerst#6
Motivation ---------- This will add types. The behaviour has changed minimally. The conditions don't check for `key in data` but simply `data.key`. I think considering the differences, it's perfectly for fine for this library. How to test ----------- 1. `npm run build` 2. Have a look in `dist/` close derhuerst#6
Motivation ---------- This will add types. The behaviour has changed minimally. The conditions don't check for `key in data` but simply `data.key`. I think considering the differences, it's perfectly for fine for this library. How to test ----------- 1. `npm run build` 2. Have a look in `dist/` close derhuerst#6
Motivation ---------- This will add types. The behaviour has changed minimally. The conditions don't check for `key in data` but simply `data.key`. I think considering the differences, it's perfectly for fine for this library. How to test ----------- 1. `npm run build` 2. Have a look in `dist/` close derhuerst#6
Hi, thanks for your cool library :) it would be even better with TypeScript support or JSDoc type annotations + DefinitelyTyped
@types/
package. Is this in the roadmap? Do you need any help with it?The text was updated successfully, but these errors were encountered: