Page MenuHomePhabricator

[landing] key competitor data
ClosedPublic

Authored by ginsu on May 30 2023, 8:00 AM.
Tags
None
Referenced Files
F3373269: D8028.id27271.diff
Tue, Nov 26, 8:39 AM
F3373003: D8028.id29735.diff
Tue, Nov 26, 8:20 AM
F3366970: D8028.id27265.diff
Mon, Nov 25, 1:11 PM
Unknown Object (File)
Sun, Nov 17, 2:19 AM
Unknown Object (File)
Sun, Nov 17, 1:36 AM
Unknown Object (File)
Sun, Nov 17, 1:36 AM
Unknown Object (File)
Sun, Nov 17, 1:36 AM
Unknown Object (File)
Sun, Nov 17, 1:36 AM
Subscribers

Details

Summary

In a subsequent diff we are going to want to access the competitor data by its key. This diff keys the competitorData so that we can do that

Depends on D8025

Test Plan

flow and this will be further tested in subsquent diffs

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

ginsu requested review of this revision.May 30 2023, 8:18 AM

If we only plan on exporting keyedCompetitorData, could we just add keys to competitorData and turn it from array -> keyed obj?

This revision is now accepted and ready to land.May 30 2023, 8:58 AM

(Looks like you added the Signal key in the update, did you mean to update the other entries as well?)

(Looks like you added the Signal key in the update, did you mean to update the other entries as well?)

Yes I will do that in each separate diff

This revision was automatically updated to reflect the committed changes.