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

feat(client): type safety for useStreaming #298

Merged
merged 1 commit into from
Jan 18, 2024
Merged

Conversation

xxshady
Copy link
Contributor

@xxshady xxshady commented Jan 18, 2024

adds second overload for constructors with useStreaming and streamingDistance so it is impossible to use useStreaming alone (leading to unwanted behavior)

adds second overload for constructors with `useStreaming` and `streamingDistance` so it is impossible to use `useStreaming` alone (leading to unwanted behavior)
@xxshady xxshady requested a review from C0kkie as a code owner January 18, 2024 17:55
@xxshady
Copy link
Contributor Author

xxshady commented Jan 18, 2024

Just noticed it would be a breaking change to use true instead of boolean for useStreaming parameter it's breaking anyway

@xLuxy xLuxy merged commit 50241a0 into altmp:dev Jan 18, 2024
1 check passed
xLuxy pushed a commit that referenced this pull request Jan 28, 2024
adds second overload for constructors with `useStreaming` and `streamingDistance` so it is impossible to use `useStreaming` alone (leading to unwanted behavior)
xLuxy pushed a commit that referenced this pull request Jan 28, 2024
adds second overload for constructors with `useStreaming` and `streamingDistance` so it is impossible to use `useStreaming` alone (leading to unwanted behavior)
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