This repository has been archived by the owner on Jun 21, 2024. It is now read-only.
capture: add support for the /batch request shape #21
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Can be reviewed commit by commit as some code is moved around before being modified
v0
with goal of being as django-compatible as reasonable. We should then start a separatev1
endpoint with less debt. Move some code around to make navigation easier/batch
request as test fixture and make it pass. Note that the node SDK has a secondform
submission type that uses lz compression 🤦 but they seem to be going to/e/
anyway, not/batch
RawRequest
instead of directly extracting events from ittoken
,sent_at
andis_historical
from theRawRequest
body, to support the/batch
fields. Theis_historical
might morph into a more genericdata_type
metadata down the road?django_compat.rs
, will add end2end tests when I implement theis_historical
handling in another PR/batch
and/e
endpoints, others will be added later on