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
TS: Rely on new web-stream-tools
types, fix SignOptions
#1502
TS: Rely on new web-stream-tools
types, fix SignOptions
#1502
Conversation
…d fix SignOptions
After this change I now get:
Should Alternatively, could you document the required types packages in the README? |
Hey @edmorley , thanks for spotting this. I wouldn't add it to the Adding the info on the readme is a good idea, feel free to open a PR :) |
@larabr I find it really strange that you do not support typescript 'officially' but do provide typings with this package. And then refuse to fix issues with that. |
@KnisterPeter We provide typings because we think it adds value, and it's better than the alternative, namely relying on https://github.com/DefinitelyTyped/DefinitelyTyped, which was done in previous versions, and was problematic since we weren't directly checking them for correctness. This specific issue is also easily fixed on the app's side. |
@larabr Thanks for your answer.
Currently it's broken and it's not easy to see how this could be fixed (besides searching all issues). It breaks the npm dependency chain.
Good to hear 😃 |
I agree searching issues is not ideal, which is why we would welcome a PR that adds info about how to integrate Typescript in the README :) |
Here we go: #1586 |
Also:
EncryptSessionKeyOptions
to make it easier to declare wrapper functions ofencryptSessionKey
.Message.getText()
and.getLiteralData()
(close Message.getText() returns a ReadableStream that is inconsistent with typedefs #1286).TODO: