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

chore: use upstream types for sub-encoder #465

Merged
merged 1 commit into from
Feb 5, 2024

Conversation

EvanHahn
Copy link
Contributor

@EvanHahn EvanHahn commented Feb 5, 2024

@types/sub-encoder was recently created so we can use that instead of defining our own type.

[@types/sub-encoder was recently created][0] so we can use that instead
of defining our own type.

[0]: DefinitelyTyped/DefinitelyTyped#68390
@EvanHahn EvanHahn merged commit 07e4b12 into main Feb 5, 2024
7 checks passed
@EvanHahn EvanHahn deleted the use-upstream-sub-encoder-types branch February 5, 2024 15:13
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