-
Notifications
You must be signed in to change notification settings - Fork 12
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
[Hold] feat(imports): Add CmsBatchImport events #562
base: main
Are you sure you want to change the base?
Conversation
7631ab9
to
03f1aa2
Compare
b1ac220
to
7e4bc6d
Compare
* { | ||
* context_module: "batchImportFlow", | ||
* context_page_owner_type: "batchImport", | ||
* context_page_owner_id: "67b646ecbe87376bfeb3f962", |
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.
Ditto here; where the partner is given the option to download we haven't yet generated an import ID. Cool if we pass an empty string here?
7e4bc6d
to
9deed32
Compare
* { | ||
* event: "csvImportError", | ||
* context_page_owner_type: "batchImport", | ||
* context_page_owner_id: "67b646ecbe87376bfeb3f962", |
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.
☝️ If there's a (fatal) error during import we don't generate an ID.
If there's a warning, where some rows can be imported, we do have an ID.
9deed32
to
139e039
Compare
|
@damassi Amended the PR after reviewing what's available in the BE.
|
Sweet, thanks @leodmz. I'll rebase and merge this! |
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.
sounds great!
The type of this PR is: Feat
Description
This updates cohesion with the new BatchImports events.
Additionally (per our discussion @leodmz) starts organizing our CMS-specific events inside of an
src/Schema/CMS
folder, mirroring how things are structured in web / ios folders:An updated organization like this will become imperative as we continue migrating CMS pages to our modern patterns and moving legacy CMS events over to cohesion.
Note that CMS interfaces/events/values have been prefixed with a
CMS
identifier. This shouldn't preclude mixing in events from other parts of the schema in an event (likeEvent.click
), only that now we can go directly to theCMS
folder not get lost in collector-specific events, and avoid type clashes.cc @artsy/amber-devs
PR Checklist (tick all before merging)
index.ts
click
andtap
(platform is inferred by the DB storing events)📦 Published PR as canary version:
4.238.1--canary.562.11138.0
✨ Test out this PR locally via: