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: adding legacy grpc lib support #9

Merged
merged 3 commits into from
Jan 7, 2023
Merged

Conversation

Farenheith
Copy link
Member

This feature allows you to use the legacy gRPC package if you need to.
Although the legacy package is deprecated, the new one presents a memory leak behavior that is yet to be solved. You can follow the issue here.

BREAKING CHANGE: The library contract needed to be changed in order to keep functionalities compatible between both versions. Although the contract must be almost equal some things like error catching have behaved differently between them. Due to that, we chose an approach that works for both packages, but we need to break the contract

BREAKING CHANGE: The library contract needed to be changed in order to keep functionalities compatible between both versions.
Although the contract must be almost equal some things like error catching have behaved differently between them. Due to that,
we chose an approach that works for both packages, but we need to break the contract.
@sonarcloud
Copy link

sonarcloud bot commented Jan 7, 2023

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@Farenheith Farenheith merged commit 45a7f3d into master Jan 7, 2023
codibrebot pushed a commit that referenced this pull request Jan 7, 2023
# [2.0.0](v1.4.0...v2.0.0) (2023-01-07)

### Features

* adding legacy grpc lib support ([#9](#9)) ([45a7f3d](45a7f3d))

### BREAKING CHANGES

* The library contract needed to be changed in order to keep functionalities compatible between both versions.
Although the contract must be almost equal some things like error catching have behaved differently between them. Due to that,
we chose an approach that works for both packages, but we need to break the contract.
@codibrebot
Copy link

🎉 This PR is included in version 2.0.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

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

Successfully merging this pull request may close these issues.

None yet

3 participants