Closed Bug 1843658 Opened 2 years ago Closed 2 years ago

ASRouter devtools "modify" method fails if message doesn't have groups property

Categories

(Firefox :: Messaging System, defect, P3)

defect

Tracking

()

RESOLVED FIXED
117 Branch
Iteration:
117.2 - July 17 - July 28
Tracking Status
firefox117 --- fixed

People

(Reporter: aminomancer, Assigned: emcminn)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

When testing feature callouts from the devtools, I noticed that it throws if the message you input lacks a groups property. You have to add "groups": [] to get it to show. We should figure out why that is and get rid of the requirement, since messages don't actually need to have a groups property. Taking the existing feature callout messages and plugging them into the devtools fails because of this. So we should definitely make sure that all existing messages in tree that work correctly in production will also work from the devtools.

will be good to check if this issue is specific to feature callout messages showing in devtool

Assignee: nobody → emcminn
Iteration: --- → 117.2 - July 17 - July 28
Priority: -- → P3

Some basic investigation seems to point to this being specific to Feature Callouts - other messages will throw the console error when the groups property is missing, but still display.

There is a simple fix for the console error, but I'm not sure if that will have an effect on the feature callout messages, since in current Nightly they don't render either way.

Pushed by emcminn@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/1b8a2d934ea2 Use optional chaining to keep addImpression from throwing an error r=aminomancer,omc-reviewers
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 117 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: