Skip to content
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

refactor: change event schema #28

Merged
merged 1 commit into from
Aug 3, 2023

Conversation

MaxFrank13
Copy link
Member

We have made changes to our event schema for experiment V1 of the Skills Builder.

This PR adds in those changes and modifies any tests as necessary to fit the new schema.

APER-2699

@codecov-commenter
Copy link

codecov-commenter commented Aug 2, 2023

Codecov Report

❗ No coverage uploaded for pull request base (main@374f695). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #28   +/-   ##
=======================================
  Coverage        ?   91.59%           
=======================================
  Files           ?       30           
  Lines           ?      369           
  Branches        ?       68           
=======================================
  Hits            ?      338           
  Misses          ?       30           
  Partials        ?        1           

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

title: rec.title,
courserun_key: rec.active_run_key,
label: rec.active_run_key || `${rec.title} [${rec.uuid}]`,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This little bit of naming logic is duplicated and also important. Should we add a comment that if the label is changed that we should also update productLabel in RecommendationCard.jsx (and vice-versa)?

Not sure if it would ever change... but seems like it would cause a weird mismatch and may be hard to track down?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good call out! I'll add a comment in both places. The schema is bound to be modified again so it'll be nice to have the reminder

Copy link
Member

@justinhynes justinhynes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changes look sane to me, even if I'm a bit out of touch with the problem space.

@MaxFrank13 MaxFrank13 force-pushed the mfrank/2699-changes-to-event-schema branch from 8f0a24d to f9b649c Compare August 3, 2023 13:12
@MaxFrank13 MaxFrank13 force-pushed the mfrank/2699-changes-to-event-schema branch from f9b649c to e724412 Compare August 3, 2023 13:17
@MaxFrank13 MaxFrank13 merged commit 5f8e8a9 into main Aug 3, 2023
3 checks passed
@MaxFrank13 MaxFrank13 deleted the mfrank/2699-changes-to-event-schema branch August 3, 2023 13:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants