React-native-gifted-chat: How to use redux to manage messages ?

[jackmatrix]

I am trying to use redux to manage my chat state, i need to keep my message state out of the component.

but when i'm using this method

GiftedChat.append(messagesInMyRedux, notificationMessage)

I'm getting this error

Warning:Value appears more than once in array

messagesinMyRedux in an array and notificationMessage is a string.

I've tried to not use GiftedChat.append and tested messagesInMyRedux.push(notificationMessage) but nothing occurs.

Any idea ?

[Unimate]

@jackmatrix
onSend(messages = []) { this.setState(previousState => ({ messages: GiftedChat.append(previousState.messages, messages), })) }
Maybe your notificationMessage must be array with message-object?

[KingCosmic]

you say your error is

Warning:Value appears more than once in array

can you provide more info? other then that

You have to dispatch the action to redux which you dont seem to be doing it would look something like

Your Reducer:

const ADD_MESSAGES = 'ADD_MESSAGES';

let dataState = {
    messages: []
}

export default chatReducer = (state = dataState , action) => {
  switch (action.type) {
    case ADD_MESSAGES:
      state.messages = GiftedChat.append(state.messages, action.messages)
      return state;
    default:
      return state;
  }
};

your Action:

const ADD_MESSAGES = 'ADD_MESSAGES';

export const addMessages = (messages) => ({
  type: ADD_MESSAGES,
  messages
})

used in onsend function:

onSend(messages = []) {
    this.props.addMessages(messages)
}

not the best examples but maybe itll get you going

[ewal]

I do not believe that you need to use Gifted chats append method for achieving what you're after.
Personally I do something like this to append new messages to the message array:

const initialState = {
  messages: [],
};

export default (state = initialState, action) => {
...
  case INCOMING_MESSAGE:
    return {
      ...state,
      messages: [action.message, ...state.messages],
    }; 
...
};

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.