Manage State Locally First - bizarre test results and trouble with the <ul>

Tell us what’s happening:

Hi, I’m having an odd problem. The only test I’m not passing is " Calling the method handleChange should update the input value in state to the current input."

The weird thing is that, as you can see, I’m logging these values in the console and to me it looks like the test should pass. The values match up after every keystroke in the input field. Also strange is that I’m pretty sure I should not be passing the test for rendering <li> elements because that’s not rendered correctly in the test window, but it shows me passing that test anyway.

I would love any help explaining why I don’t pass the handlechange test, why I do pass the list test, or how I can fix my list so that it really does render properly (instead of just passing the test while being broken).

Your code so far

class DisplayMessages extends React.Component {
  constructor(props) {
    this.state = {
      input: '',
      messages: []

    this.handleChange = this.handleChange.bind(this);
    this.submitMessage = this.submitMessage.bind(this);
  // add handleChange() and submitMessage() methods here
  handleChange(event) {
    this.setState(Object.assign(this.state, {input:}));
  submitMessage() {
    let newMessages = this.state.messages.concat([this.state.input]);
    this.setState({input: "", messages: newMessages});

  render() {
    const renderedMessages = => "<li>" + msg + "</li>");
    //this might need to be converted to a string instead of an array ^ 
    return (
        <h2>Type in a new Message:</h2>
        { /* render an input, button, and ul here */ }
        <input value={this.state.input} onChange={this.handleChange} />
        <button onClick={this.submitMessage}>button</button>
        { /* change code above this line */ }

Your browser information:

User Agent is: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/75.0.3770.100 Safari/537.36.

Link to the challenge:

You should use setState to manipulate the state in your methods. What’s the point of using object.assign there? You are directly assigning to this.state outside of a constructor, this is a big no no in react. Changing this will let you pass the handleChange test.

Lists work with arrays, so you are correct here in choosing a map … But you should use JSX to render proper html. Something like this works well:


As for why are you passing the list test? Idk, probably because it’s not comprehensive enough… :stuck_out_tongue:

I mistakenly thought that Object.assign left the arguments untouched and returned a new object. The reason I did it is because I thought this.setState({input:}) would erase the messages property in the state. So there were a couple things I misunderstood in a pretty big way here. Thanks!

1 Like

FYI - The reason you were passing the 2nd test when you should not have been, was because the production site code was not actually testing if the li element was present when a new item was added. This has been fixed on the repo’s master branch and will work correctly once the master branch of the repo has been deployed to production (hopefully in the coming weeks).

1 Like