-
Notifications
You must be signed in to change notification settings - Fork 624
Expose the transport factory as a Qualified dependency #5237
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
Conversation
Release note changesThe following had changelogs that were modified, but did not have any unreleased entries for release notes to generate from. Changelogsfirebase-datatransport |
Coverage Report 1Affected Products
Test Logs |
Size Report 1Affected Products
Test Logs |
Startup Time Report 1Note: Layout is sometimes suboptimal due to limited formatting support on GitHub. Please check this report on GCS. Notes
Startup Times
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code looks fine, curious about the versioning situation
* Expose the transport factory as a Qualified dependency. * Add CHANGELOG entry * Fix version bump.
The datatransport factory was exposed as a single, unqualified component.
Now it's exposed as both the unqualified component, to maintain backwards compatibility, and two qualified components with matching endpoints.