-
Notifications
You must be signed in to change notification settings - Fork 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
feat: allow backend to specify a custom analytics endpoint #831
Conversation
Size Change: +904 B (0%) Total Size: 710 kB
ℹ️ View Unchanged
|
f9a474a
to
e5ab7f9
Compare
44b19f3
to
a09ebff
Compare
@@ -46,68 +42,3 @@ describe('compressData()', () => { | |||
expect(given.subject).toMatchSnapshot() | |||
}) | |||
}) | |||
|
|||
describe('Payload Compression', () => { |
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.
removing as it's already covered by the tests in decide.js
+ posthog-core.js
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.
makes sense! 🚀
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.
🚀
Changes
analytics.endpoint
field in the decide response to allow us to slowly move posthog-js traffic to the new intake endpointChecklist