Skip to content

fix: data field in DataTransferRequest objects is optional #134

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

Merged
merged 1 commit into from
Jan 13, 2025

Conversation

j-white
Copy link
Contributor

@j-white j-white commented Dec 19, 2024

the data field on the DataTransfer* messages is optional

unfortunately a breaking change 😀

Copy link
Member

@parberge parberge left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me, but I think @tommymalmqvist will have to review it as well.

@parberge
Copy link
Member

parberge commented Dec 20, 2024

the data field on the DataTransfer* messages is optional

unfortunately a breaking change 😀

Is it really a breaking change though? Since it should be backward compatible if I understand the code (which is likely that I don't 😄 ). But please let me know your thoughts here.

Copy link

codecov bot commented Dec 20, 2024

Codecov Report

Attention: Patch coverage is 80.95238% with 4 lines in your changes missing coverage. Please review.

Project coverage is 81.67%. Comparing base (95e628b) to head (dd71f4a).
Report is 2 commits behind head on main.

Files with missing lines Patch % Lines
src/tests/schema_validation/v2_0_1.rs 80.95% 4 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #134      +/-   ##
==========================================
- Coverage   81.68%   81.67%   -0.02%     
==========================================
  Files          51       51              
  Lines        4347     4366      +19     
==========================================
+ Hits         3551     3566      +15     
- Misses        796      800       +4     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@parberge
Copy link
Member

Codecov Report

Attention: Patch coverage is 80.95238% with 4 lines in your changes missing coverage. Please review.

Project coverage is 81.67%. Comparing base (1a6af0f) to head (47a288f).
Report is 1 commits behind head on main.

Files with missing lines Patch % Lines
src/tests/schema_validation/v2_0_1.rs 80.95% 4 Missing ⚠️
Additional details and impacted files
☔ View full report in Codecov by Sentry. 📢 Have feedback on the report? Share it here.

I don't know what's up with our test coverage. I suspect something is not working properly. Tried to fix it in #132 but I don't have enough technical skill to know what the problem is.

@j-white
Copy link
Contributor Author

j-white commented Dec 20, 2024

Is it really a breaking change though? Since it should be backward compatible if I understand the code (which is likely that I don't 😄 ). But please let me know your thoughts here.

If someone is already creating DataTransferRequest objects today, then this will break their code on upgrade. So safer to increment to major version for release.

@j-white j-white changed the title data field in DataTransferRequest objects is optional fix: data field in DataTransferRequest objects is optional Dec 31, 2024
@tommymalmqvist tommymalmqvist merged commit f655062 into codelabsab:main Jan 13, 2025
2 of 3 checks passed
@j-white j-white deleted the jw/datatransfer branch January 13, 2025 14:03
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.

3 participants