[🐛] Text not available in useMessageInputContext

[iAhtasham]

Issue

Hello I have been working on almost 4 different versions of stream chat react native, all the way from 6.5 to 8.4

In version 8.x, the text state is not exposed in the useMessageInputContext, so if we try to make custom ui, we are not able to get the actual text, there is a work-around to use the inputRef.current which is exposed and can be used to get the current message typed.

Steps to reproduce

Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error
   etc...

Expected behavior

Project Related Information

Customization

Click To Expand

 const { text, setText, sendMessage, uploadNewFile, closeAttachmentPicker } = useMessageInputContext();

Offline support

• I have enabled offline support.
• The feature I'm having does not occur when offline support is disabled. (stripe out if not applicable)

Environment

Click To Expand

package.json:

# N/A

react-native info output:

 OUTPUT GOES HERE

• Platform that you're experiencing the issue on:
  • iOS
  • Android
  • iOS but have not tested behavior on Android
  • Android but have not tested behavior on iOS
  • Both
• stream-chat-react-native version you're using that has this issue:
  • e.g. 5.4.3
• Device/Emulator info:
  • I am using a physical device
  • OS version: e.g. Android 10
  • Device/Emulator: e.g. iPhone 11

Additional context

Screenshots

Click To Expand

---

[khushal87]

Hey @iAhtasham, you can always use the Message Composer to get the state of the text wherever you want inside the Channel using on V8. As you have rightly pointed out this is not available through context anymore for performance reasons.

const textComposerStateSelector = (state: TextComposerState) => ({
  text: state.text,
});

const Component = () => {
  const messageComposer = useMessageComposer();
  const { textComposer } = messageComposer;
  const { text } = useStateStore(textComposer.state, textComposerStateSelector);
}

[iAhtasham]

Hey @iAhtasham, you can always use the Message Composer to get the state of the text wherever you want inside the Channel using on V8. As you have rightly pointed out this is not available through context anymore for performance reasons.

const textComposerStateSelector = (state: TextComposerState) => ({
text: state.text,
});

const Component = () => {
const messageComposer = useMessageComposer();
const { textComposer } = messageComposer;
const { text } = useStateStore(textComposer.state, textComposerStateSelector);
}

if possible, could you guys update the documentation and sample apps?