Page MenuHomePhabricator

[native] Move 'InlineEngagement' styling from 'ComposedMessage' to component
ClosedPublic

Authored by kuba on Mar 14 2023, 1:38 AM.
Tags
None
Referenced Files
Unknown Object (File)
Sun, Nov 10, 1:33 PM
Unknown Object (File)
Sun, Nov 10, 10:26 AM
Unknown Object (File)
Sun, Nov 10, 10:17 AM
Unknown Object (File)
Sun, Nov 10, 9:57 AM
Unknown Object (File)
Sun, Nov 10, 9:15 AM
Unknown Object (File)
Wed, Nov 6, 3:10 AM
Unknown Object (File)
Wed, Nov 6, 2:52 AM
Unknown Object (File)
Wed, Nov 6, 2:52 AM
Subscribers

Details

Summary

Move 'InlineEngagement' styling from 'ComposedMessage' to 'InlineEngagement' component to make it concise with the web version. It makes it also easier to add message labels to the code, so they were in the 'InlineEngagement' component, like on the web.

Test Plan

Checked if everything works after the changes. Nothing visible should change. Compared how reactions and threads are rendered in iOS and Android simulators with the old
version.

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

native/chat/inline-engagement.react.js
125–132 ↗(On Diff #24070)

Why can't this be inlined in line 146? Is this memo necessary?

native/chat/inline-engagement.react.js
125–132 ↗(On Diff #24070)

Here it probably could be inlined. But I prepared it for the next diff: https://phab.comm.dev/D7065 (which still requires some changes, which will partly answer this question).

inka added inline comments.
native/chat/inline-engagement.react.js
125–132 ↗(On Diff #24070)

I see, thank you

This revision is now accepted and ready to land.Mar 29 2023, 12:41 AM