Data Connect: Add support for web framework tracking via custom headers#8749
Data Connect: Add support for web framework tracking via custom headers#8749
Conversation
🦋 Changeset detectedLatest commit: 99cced0 The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Vertex AI Mock Responses Check
|
Size Report 1Affected Products
Test Logs |
Size Analysis Report 1This report is too large (70,082 characters) to be displayed here in a GitHub comment. Please use the below link to see the full report on Google Cloud Storage.Test Logs |
DellaBitta
left a comment
There was a problem hiding this comment.
Could you add a Changset please?
Changeset File Check ✅
|
.changeset/little-news-sniff.md
Outdated
| 'firebase': minor | ||
| --- | ||
|
|
||
| Add custom request headers based on type of SDK calling Core SDK |
There was a problem hiding this comment.
This will become release notes shortly. Could you rephrase this with our users in mind. Maybe something like:
Changed: Add custom request headers based on the type of SDK (TanStack, Angular, etc) that's invoking Data Connect requests. This will help us something something.
There was a problem hiding this comment.
Done - let me know what you think
Add support for web framework tracking via custom headers
CallerSdkTypeEnumenum to differentiate between frameworks_callerSdkTypefield and_setCallerSdkType()methods toDataConnecttype, as well asDataConnectTransporttypes_isUsingGenfields and functions (_isUsingGen = falseis now represented byCallerSdkTypeEnum.Base, while_isUsingGen = trueis represented by any value other thanCallerSdkTypeEnum.Base)