Page MenuHomePhabricator

[web] implement new InlineEngagement design
ClosedPublic

Authored by ginsu on Jan 19 2023, 9:29 PM.
Tags
None
Referenced Files
Unknown Object (File)
Wed, Jun 19, 7:07 PM
Unknown Object (File)
Fri, Jun 14, 2:23 AM
Unknown Object (File)
Thu, Jun 13, 3:11 PM
Unknown Object (File)
Thu, Jun 13, 11:59 AM
Unknown Object (File)
Wed, Jun 12, 10:29 PM
Unknown Object (File)
Tue, Jun 11, 11:12 PM
Unknown Object (File)
Fri, Jun 7, 7:17 AM
Unknown Object (File)
Fri, Jun 7, 6:33 AM
Subscribers

Details

Summary

implemented new InlineEngagement design. The new design splits the InlineEngagement into two seperate parts

Screenshot 2023-01-19 at 5.50.52 PM.png (1×1 px, 139 KB)


Depends on D6317 and D6302
Linear Task: ENG-2720

Test Plan

Please watch the demo video to see the new InlineEngagement

Diff Detail

Repository
rCOMM Comm
Branch
eng-2465 (branched from master)
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

ginsu requested review of this revision.Jan 19 2023, 9:43 PM

Looks good, minor notes inline.

web/chat/inline-engagement.react.js
27 ↗(On Diff #21207)

Do we really need this? Are we not able to check the truthiness of ThreadInfo directly in threadsContainerClasses and reactionsContainerClasses?

28 ↗(On Diff #21207)

Could we replace this with

const reactionsExist = reactions?.size > 0;

?

Could we also move threadInfoExists and reactionsExist directly above threadsContainerClasses and reactionsContainerClasses so they're closer to usage?

This revision is now accepted and ready to land.Jan 24 2023, 10:14 AM
web/chat/inline-engagement.react.js
28 ↗(On Diff #21207)

Getting a flow error about cannot comparing undefined to number when attempting to replace reactionsExist with the statement you provided

web/chat/inline-engagement.react.js
28 ↗(On Diff #21207)

Oh yeah that makes sense never mind

This revision was automatically updated to reflect the committed changes.