Skip to content
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

adjust type definitions to allow browser usage #58

Merged
merged 1 commit into from
Jun 22, 2020

Conversation

gyzerok
Copy link
Contributor

@gyzerok gyzerok commented Jun 19, 2020

Hello!

Current type definitions expect Buffer, however implementation does not require it. Since the library supports browsers, type definitions need to be more relaxed to allow browser usage without compilation errors :)

@gyzerok gyzerok changed the title adjust type definitions to reflect browser support adjust type definitions to allow browser usage Jun 19, 2020
@aadsm aadsm merged commit 37f958c into aadsm:master Jun 22, 2020
@aadsm
Copy link
Owner

aadsm commented Jun 22, 2020

I'm not 100% convinced (tbh I don't have the time right now to fully check) but after seeing your work on the vscode issue I trust you!

@aadsm
Copy link
Owner

aadsm commented Jun 22, 2020

I'll probably only be able to ship a new version next weekend, I'll still try to do it over the week though.

@gyzerok
Copy link
Contributor Author

gyzerok commented Jun 22, 2020

Hello @aadsm and thanks a lot for merging!

I based my type definition adjustments on the fact that you convert to the string internally. Also you are using strings in your tests and in your readme.

Does this sound sensible?

@gyzerok gyzerok deleted the patch-1 branch June 22, 2020 08:09
@aadsm
Copy link
Owner

aadsm commented Jun 22, 2020

Oh I see, yeah. Thanks for pointing out the code!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants