Closed Bug 1709602 Opened 1 year ago Closed 1 year ago

Review React integration of UX Actions

Categories

(Webtools Graveyard :: Pontoon, task, P2)

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: axel, Assigned: mathjazz)

References

Details

(Whiteboard: pontoon-notification-experiments)

Attachments

(1 file)

I still have some open questions on the React integration of logging UX Actions. Sorry for my ignorance in most of them, I'm learning React the wrong way around.

Filing a follow-up bug to track them.

I'm talking about the frontend pieces of https://github.com/mozilla/pontoon/search?q=loguxaction.

Is core/api/user the right place for the API?

What does it mean that we have an API wrapper in core/user/actions? Does that imply that there's state?

What does it mean that logUxAction goes through UserControls? That, and just that.

To sketch an alternative scenario, what would it mean if we had core/api/uxaction.js, and called that directly from UserNotificationsMenu ?

Sorry April for bugging you first with this ;-)

Flags: needinfo?(abowler2)
Assignee: nobody → m
Status: NEW → ASSIGNED
Priority: -- → P2
Whiteboard: pontoon-notification-experiments
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Flags: needinfo?(abowler)
Product: Webtools → Webtools Graveyard
You need to log in before you can comment on or make changes to this bug.