enzyme@3: wrapper is not updated even if there was a new render #1153

deepsweet · 2017-09-26T19:57:39Z

Hi. Just faced this after updating to v3.

Given the following deps:

├─ enzyme-adapter-react-16@1.0.0
├─ enzyme@3.0.0
├─ react-dom@16.0.0
├─ react-test-renderer@16.0.0
└─ react@16.0.0

And the HOC:

import React, { Component } from 'react'

const testHOC = (Target) => class TestClass extends Component {
  constructor (...args) {
    super(...args)

    this.state = {}
    this.onTest = this.onTest.bind(this)
  }

  onTest () {
    this.setState({
      foo: true
    })
  }

  render () {
    console.log(this.state)

    return (
      <Target {...this.props} {...this.state} onTest={this.onTest} />
    )
  }
}

export default testHOC

And the test:

import React from 'react'
import { mount } from 'enzyme'
import testHOC from './testHOC'

describe('testHOC', () => {
  it('should work', () => {
    const Target = () => null
    const EnhancedTarget = testHOC(Target)
    const wrapper = mount(
      <EnhancedTarget />
    )

    wrapper.find(Target).prop('onTest')()

    console.log(
      wrapper.debug()
    )
  })
})

I see:

  console.log testHOC.js:18
    { foo: true }

  console.log testHOC.spec.js:15
    <TestClass>
      <Target onTest={[Function]} />
    </TestClass>

So the was a new render, but wrapper just didn't react to it. Works fine with v2.

Please correct me if I was wrong all this time and test should be written in another way.

The text was updated successfully, but these errors were encountered:

ljharb · 2017-09-26T20:00:31Z

Wrappers are immutable in enzyme 3; this is in the migration docs.

Try wrapper.update() after invoking your function.

deepsweet · 2017-09-26T20:01:32Z

Already tried and now re-tried, same result.

j4k · 2017-09-26T22:35:13Z

I'm also experiencing the same behaviour with the same deps on some of my component tests (non-HOC) where the state updates, but the wrapper does not, even after calling .update().

Placing console.log's in the component under tests render method show's things rendering correctly during the test, I just can't seem to assert properly after an .update(), .debug() outputs the initial component. .state() shows the correct state after an .update()

yesmeck · 2017-09-27T03:42:42Z

I'm also experiencing the similar behavior when using conditional rendering, here is a reproduction repo https://github.com/yesmeck/enzyme-set-props-bug.

yesmeck · 2017-09-27T03:49:19Z

I created a separate issue #1163.

mx-scissortail · 2017-09-27T17:15:24Z

Same issue. I can confirm that render is running appropriately, and I can even get the updated values from wrapper.state, but wrapper.update doesn't reflect the re-rendered component.

iantanwx · 2017-09-28T05:41:42Z

Same issue here.

gziolo · 2017-09-29T09:23:01Z

I did some heave debugging for WordPress/gutenberg#2813 and it looks like we are having the same kind of issues that are reported in this thread and here.

I tried to add recommended wrapper.update(); call after the click event is simulated, but it didn't help. It's quite interesting scenario because the part of the component that depends on the component's state (https://github.com/WordPress/gutenberg/blob/ad316ab1f8cfe60aeeb45ff27d45336bfb214c3c/editor/inserter/menu.js#L384) gets properly updated, but the other part (https://github.com/WordPress/gutenberg/blob/ad316ab1f8cfe60aeeb45ff27d45336bfb214c3c/editor/inserter/menu.js#L366) which also is conditionally rendered based on the components' state doesn't show up in the output of wrapper.debug() call. When I debugged it turned out that React component does everything properly behind the scenes. It looks like Enzyme gets out of sync.

tleunen · 2017-09-29T18:03:07Z

Confirmed what @gziolo said. The component is updated properly. .html() returns the right structure. But the ReactWrapper itself is out of sync.

lelandrichardson · 2017-10-03T05:51:45Z

This is hopefully fixed in enzyme-adapter-react-16@1.0.1. Please upgrade and let us know if it does not fix your issue. Thanks!

mrbinky3000 · 2017-11-27T21:01:33Z

This seems to still be an issue in enzyme-adapter-react-16@1.1.0 wrapper.update() does not work. Yet console logs in the source code show that state is being updated. .html() shows the correct structure. I can point you to a repo with the failing test if that helps.

ljharb · 2017-11-28T00:41:17Z

@mrbinky3000 .html() isn't as useful as .debug(), what does that show?

mrbinky3000 · 2017-11-28T14:39:44Z

ImageWithZoom has a state property named "hovering". It starts off false as expected.

  console.log src/ImageWithZoom/ImageWithZoom.jsx:89
    ImageWithZoom.render() state { isImageLoading: false,
      hovering: false,
      style: {},
      x: null,
      y: null }

This is a debug() dump of the wrapper before the mouseover event.

  console.log src/ImageWithZoom/__tests__/ImageWithZoom.test.jsx:38
    before mouseover debug:
     <ImageWithZoom src="bob.jpg" tag="div">
      <div className="container">
        <Wrapper className="image carousel__zoom-image" tag="div" src="bob.jpg" isBgImage={true} onLoad={[Function]} onError={[Function]}>
          <Image hasMasterSpinner={false} orientation="horizontal" className="image carousel__zoom-image" tag="div" src="bob.jpg" isBgImage={true} onLoad={[Function]} onError={[Function]} carouselStore={{...}} alt="" height={{...}} renderError={{...}} renderLoading={{...}} style={{...}}>
            <div className="image carousel__image carousel__image--with-background carousel__image--success image carousel__zoom-image" style={{...}} orientation="horizontal" height={{...}} />
          </Image>
        </Wrapper>
        <Wrapper className="overlay carousel__zoom-image-overlay" tag="div" src="bob.jpg" style={{...}} isBgImage={true} onMouseOver={[Function]} onMouseOut={[Function]} onMouseMove={[Function]}>
          <Image hasMasterSpinner={false} orientation="horizontal" className="overlay carousel__zoom-image-overlay" tag="div" src="bob.jpg" style={{...}} isBgImage={true} onMouseOver={[Function]} onMouseOut={[Function]} onMouseMove={[Function]} carouselStore={{...}} alt="" height={{...}} onError={{...}} onLoad={{...}} renderError={{...}} renderLoading={{...}}>
            <div className="image carousel__image carousel__image--with-background carousel__image--success overlay carousel__zoom-image-overlay" style={{...}} orientation="horizontal" onMouseOver={[Function]} onMouseOut={[Function]} onMouseMove={[Function]} height={{...}} />
          </Image>
        </Wrapper>
      </div>
    </ImageWithZoom>

This is the .html() of the wrapper before the mouseover event is triggered.

  console.log src/ImageWithZoom/__tests__/ImageWithZoom.test.jsx:39
    before mouseover html:
     <div class="container"><div class="image carousel__image carousel__image--with-background carousel__image--success image carousel__zoom-image" orientation="horizontal" style="background-image: url(bob.jpg); background-size: cover;"></div><div class="image carousel__image carousel__image--with-background carousel__image--success overlay carousel__zoom-image-overlay" orientation="horizontal" style="background-image: url(bob.jpg); background-size: cover;"></div></div>

This is a console log in the ImageWithZoom component to acknowledge that our mouseover method was called. It sets the state property "hovering" to true.

  console.log src/ImageWithZoom/ImageWithZoom.jsx:41
    ImageWithZoom.handleOnMouseOver()

This console log is from the ImageWithZoom render method. It shows that the "hovering" state property is now true, as expected.

  console.log src/ImageWithZoom/ImageWithZoom.jsx:89
    ImageWithZoom.render() state { isImageLoading: false,
      hovering: true,
      style: {},
      x: null,
      y: null }

This .html() dump shows that the component has added the class 'carousel__zoom-image-overlay--hovering' in response to the state property "hovering" now being true.

  console.log src/ImageWithZoom/__tests__/ImageWithZoom.test.jsx:41
    after mouseover html:
     <div class="container"><div class="image carousel__image carousel__image--with-background carousel__image--success image carousel__zoom-image" orientation="horizontal" style="background-image: url(bob.jpg); background-size: cover;"></div><div class="image carousel__image carousel__image--with-background carousel__image--success overlay carousel__zoom-image-overlay hover carousel__zoom-image-overlay--hovering" orientation="horizontal" style="background-image: url(bob.jpg); background-size: cover;"></div></div>

However, Enzyme has not been updated to reflect the state change. The css class "carousel__zoom-image-overlay--hovering" is missing. Hence, my tests fail.

  console.log src/ImageWithZoom/__tests__/ImageWithZoom.test.jsx:42
    after mouseover debug
     <ImageWithZoom src="bob.jpg" tag="div">
      <div className="container">
        <Wrapper className="image carousel__zoom-image" tag="div" src="bob.jpg" isBgImage={true} onLoad={[Function]} onError={[Function]}>
          <Image hasMasterSpinner={false} orientation="horizontal" className="image carousel__zoom-image" tag="div" src="bob.jpg" isBgImage={true} onLoad={[Function]} onError={[Function]} carouselStore={{...}} alt="" height={{...}} renderError={{...}} renderLoading={{...}} style={{...}}>
            <div className="image carousel__image carousel__image--with-background carousel__image--success image carousel__zoom-image" style={{...}} orientation="horizontal" height={{...}} />
          </Image>
        </Wrapper>
        <Wrapper className="overlay carousel__zoom-image-overlay" tag="div" src="bob.jpg" style={{...}} isBgImage={true} onMouseOver={[Function]} onMouseOut={[Function]} onMouseMove={[Function]}>
          <Image hasMasterSpinner={false} orientation="horizontal" className="overlay carousel__zoom-image-overlay" tag="div" src="bob.jpg" style={{...}} isBgImage={true} onMouseOver={[Function]} onMouseOut={[Function]} onMouseMove={[Function]} carouselStore={{...}} alt="" height={{...}} onError={{...}} onLoad={{...}} renderError={{...}} renderLoading={{...}}>
            <div className="image carousel__image carousel__image--with-background carousel__image--success overlay carousel__zoom-image-overlay" style={{...}} orientation="horizontal" onMouseOver={[Function]} onMouseOut={[Function]} onMouseMove={[Function]} height={{...}} />
          </Image>
        </Wrapper>
      </div>
    </ImageWithZoom>

Here is the test.

  it('should add hovering classes to the overlay when mouse is hovering', () => {
    expect(imageWithZoom.find('div.overlay').hasClass('hover')).toBe(false);
    expect(imageWithZoom.find('div.overlay').hasClass('carousel__zoom-image-overlay--hovering')).toBe(false);

    console.log('before mouseover debug:\n', imageWithZoom.debug());
    console.log('before mouseover html:\n', imageWithZoom.html());
    imageWithZoom.find('Wrapper.overlay').simulate('mouseover');
    wrapper.update(); // doesn't matter if this is here or not, it still fails the test.
    console.log('after mouseover html:\n', imageWithZoom.html());
    console.log('after mouseover debug\n', imageWithZoom.debug());

    expect(imageWithZoom.find('div.overlay').hasClass('hover')).toBe(true);
    expect(imageWithZoom.find('div.overlay').hasClass('carousel__zoom-image-overlay--hovering')).toBe(true);
  });

I made a branch in my repo that you can check out if you need it.
https://github.com/express-labs/pure-react-carousel/tree/share/sharing-with-enzyme-author

ljharb · 2017-11-29T08:11:41Z

@mrbinky3000 thanks; can you file this separately?

mrbinky3000 · 2017-11-29T14:37:55Z

@ljharb I created issue #1400

Thanks for looking into this.

- enzymejs/enzyme#1153 (comment)

mrt123 · 2018-01-11T11:23:16Z

This is (actually isn't ... see update below) still an issue in:
"enzyme": "^3.3.0",
"enzyme-adapter-react-16": "^1.1.1",
"react-test-renderer": "^16.2.0",

In my case, component triggers a fetch in componentDidMount, which is mocked and confirmed to get triggered. Also tested component successfully re-renders during test.

wrapper.debug() still returns outdated components, and assertions fail.

 jest.spyOn(global, 'fetch').mockImplementation(() => Promise.resolve({
		json: () => myData,
}));

it('renders Dashboard with Loader active', () => {
	const wrapper = mount(<Dashboard />);
	wrapper.update();
	// console.log(wrapper.debug());
	expect(wrapper.find('Dashboard')).toHaveLength(1);
	expect(wrapper.find('RouteContentLoader')).toHaveLength(0);  // This still returns 1
	expect(wrapper.find(SpinnerSvg1)).toHaveLength(0);    // This still returns 1
});

----- UPDATE:
This does not appear to be an issue anymore. Problem was due to my own implementation. In order to update the wrapper I had to ensure promise provided in the fetch mock is fully resolved (which depending on implementation may require multiple then callbacks):

const metrics = { myStuff: 1 };

const dataPromise = Promise.resolve({
	json: () => metrics,
});
jest.spyOn(global, 'fetch')
	.mockImplementation(() => dataPromise);
//.....

// in test
	return dataPromise.then().then(() => {
		wrapper.update();  // will only work if called in last then callback
		//expect(wrapper....);
	});

mkermani144 · 2018-01-28T05:46:19Z

This no longer seems to be an issue for me in the following versions:

enzyme: 3.3.0
enzyme-adapter-react-16: 1.1.1
react-test-renderer: 16.2.0

I had exactly the same issue with shallow and wrapper.update() solved the problem. The problem was that I was updating state by calling some props of the wrapper children and enzyme didn't know that some state changes may happen, so it didn't update automatically (as stated here).

Duskfall · 2018-04-13T14:08:20Z

Same problem here.
setState is inside the method I am trying to test.
So when calling the method from the test and even when I do a wrapper.update the state of the component isn't updated. I have tried both with mount and shallow

test.js

const wrapper = shallow(<Panel {...props} />);
const appInstance = wrapper.instance();

appInstance.handleChange(data);

panel.js

handleChange(data){
   this.setState({
       test: data
   })
}

maloguertin · 2018-08-07T19:38:04Z

Is this supposed to be fixed?

I have this code:

const wrapper = mount(<Component/>)
// simulate event
console.log(wrapper.html())
console.log('length', wrapper.find('.edit-choice').length)

results:

//html()
//includes element with className edit-choice

//wrapper.find()
//length 0

ljharb · 2018-08-07T21:11:24Z

@maloguertin it's pretty hard to tell when you elide parts of the code; however it's likely that you need a wrapper.update() after you simulate the event. Separately, use .debug(), not .html(), since the latter does a full render.

ljharb · 2018-09-01T15:50:57Z

This is an old issue that's very long, and there's been numerous updates since all of the comments.

I'm going to close this, since it's not clear to me what's still broken.

If you're still having trouble, please do file a new issue, with a clear repro step, filling out the template - and we'll get it addressed ASAP.

lucasdeassis · 2018-09-03T22:24:14Z

Tried all suggestions here and didn't work. At the end updating to "enzyme-adapter-react-16": "^1.3.1" worked.

guofei0723 · 2018-12-14T09:40:15Z

"react": "^16.4.1",
"enzyme": "^3.7.0",
"enzyme-adapter-react-16": "^1.7.0",

same issue

update
it is not the same issue in my case. enzyme does not output the error message which happened in render() of my component, and that makes looks like does not re-render

ljharb · 2018-12-14T23:51:22Z

@guofei0723 please file a new issue if you're having trouble.

pvanny1124 · 2019-01-06T08:10:28Z

I see. But update() in itself isn't reflecting the state change made from a simulated event. is there a workaround without using await? i have the most recent versions: "enzyme": "^3.8.0", "enzyme-adapter-react-16": "^1.7.1", "enzyme-to-json": "^3.3.5", "jest": "^23.6.0",

…

On Sun, Jan 6, 2019 at 2:49 AM Jordan Harband ***@***.***> wrote: @pvanny1124 <https://github.com/pvanny1124> Note that doesn’t do what you expect - you’re awaiting a non-promise, so all that does is adds an extra tick. If that works for you, then all that means is that you’re winning your race condition. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1153 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AZJcoYbpA8wICdaysdD5Gt-iCkARmGCQks5vAaqhgaJpZM4Pky8j> .

pvanny1124 · 2019-01-06T08:11:03Z

also, here's the full code of what im doing: it("does not create an account for a user if an error occured", async () => { let fakeSignupErrorMethod = (last, first, email, password, auth_type, school_code, school_license_key) => { return new Promise((resolve, reject) => { reject({ errors: [{message: "error"}] }); }); } wrapper = shallow( <Signup signupMethod={fakeSignupErrorMethod} /> ); signupWrapper = wrapper.at(1).shallow().dive(); await signupWrapper.find(".Submit").find(".Submit_Button").simulate('click' ); await signupWrapper.update(); expect(signupWrapper.state("uiErrorMessages")).toEqual([ { message: "error" } ]); })

…

On Sun, Jan 6, 2019 at 3:10 AM Patrick Vanegas ***@***.***> wrote: I see. But update() in itself isn't reflecting the state change made from a simulated event. is there a workaround without using await? i have the most recent versions: "enzyme": "^3.8.0", "enzyme-adapter-react-16": "^1.7.1", "enzyme-to-json": "^3.3.5", "jest": "^23.6.0", On Sun, Jan 6, 2019 at 2:49 AM Jordan Harband ***@***.***> wrote: > @pvanny1124 <https://github.com/pvanny1124> Note that doesn’t do what > you expect - you’re awaiting a non-promise, so all that does is adds an > extra tick. If that works for you, then all that means is that you’re > winning your race condition. > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <#1153 (comment)>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AZJcoYbpA8wICdaysdD5Gt-iCkARmGCQks5vAaqhgaJpZM4Pky8j> > . >

ljharb · 2019-01-06T08:28:32Z

Whatever async stuff you’re doing in your component, you have to intercept in your tests so that you can reliably await that.

If you have further questions, please file a new issue.

Finesse · 2019-02-10T05:09:14Z

I had a similar issue. I fixed it by the following replacement:

  const wrapper = mount(<Component />);
  const button = wrapper.find('.button');
  // Do some stuff with the button...
- button.update();
+ wrapper.update();
- expect(button.prop('type')).toEqual('foo');
+ expect(wrapper.find('.button').prop('type')).toEqual('foo');

The .update() method must be called on the root wrapper, not on a child wrapper. The method mutates the root wrapper but doesn't mutate any child wrapper so I have to find the button again.

ljharb · 2019-02-10T05:11:27Z

@Finesse yes, that's part of v3 - you always have to re-find from the root.

Jlevett · 2019-03-11T04:31:35Z

I found something that works.
Add these middle two lines.

wrapper .find(...Your thing) .simulate('click'); //Click event on wrapper
await wrapper.instance().forceUpdate(); //THIS ONE
wrapper.update();  //AND THIS ONE
expect(....).toHaveLength(1); //Your assertion here

Finesse · 2019-03-11T06:25:47Z

@Jlevett Calling forceUpdate can spoil your test because React may skip updates in some cases and you need to check that React has or hasn't skipped the update.

RaiVaibhav · 2019-09-19T15:30:44Z

@Finesse Thanks for the explanation. It's mention in the guide but getting a conclusion like this
The method mutates the root wrapper but doesn't mutate any child wrapper so I have to find the button again was pretty tough for me, It was blocking me entirely

brendangibson · 2019-10-01T18:43:02Z

FWIW I was having the same issue. The I added the done parameter to the it function and called it at the end, and that fixed my problem.

it('does something', done => { .... done()})

guruusingh2033 · 2020-02-27T11:30:08Z

I am having issue. could you help me please.
componentDidMount() updating the state vale and then a Array.map() renders list of dropdown ,that means new render should be generated but i am unable to get that updated wrapper .
I want to get those dropdown items to simulate click and test method of react component .

"enzyme": "^3.11.0",

"enzyme-adapter-react-16": "^1.15.2",

"react": "^16.8.6",

"react-router-dom": "^4.2.2",

"react-test-render": "^1.1.2"

ljharb · 2020-02-27T18:57:02Z

@guruusingh2033 i'd suggest avoiding simulate entirely; but please file a new issue with more detail if you're still having trouble.

guruusingh2033 · 2020-02-28T05:43:18Z

@ljharb thanks for reading
Here is the wrapper

const wrapper = mount(
    <Provider store={configureStore()}>
      <IntlProvider
        locale={currentAppLocale.locale}
        messages={currentAppLocale.messages}
      >
        <MemoryRouter initialEntries={["/list"]}>
          <ListPage match={{ url: "localhost:3000", path: "list" }} location={{ state: undefined }} />
        </MemoryRouter>
      </IntlProvider>
    </Provider>
);

How can I test async method of ListPage component/wrapper while I am not getting updated wrapper

ljharb · 2020-02-28T05:53:59Z

@guruusingh2033 for one, pass the Providers and MemoryRouter using wrappingComponent, so that you're wrapping ListPage directly.

guruusingh2033 · 2020-02-28T05:58:21Z

@guruusingh2033 for one, pass the Providers and MemoryRouter using wrappingComponent, so that you're wrapping ListPage directly.

Could you share any reference/link please ?

ljharb · 2020-02-28T06:06:23Z

See the API docs.

ljharb added question v3 bugs labels Sep 26, 2017

ljharb assigned lelandrichardson Sep 26, 2017

deepsweet mentioned this issue Sep 28, 2017

React 16 deepsweet/hocs#6

Closed

3 tasks

gziolo mentioned this issue Sep 29, 2017

Upgrade some dependencies: React 16, Enzyme 3 and Jest WordPress/gutenberg#2813

Closed

4 tasks

marvinpinto mentioned this issue Sep 30, 2017

Fix node resolving in React 16 adapter #1169

Merged

tobilen mentioned this issue Sep 30, 2017

Upgrade to react 16 joshwcomeau/react-flip-move#191

Merged

lelandrichardson closed this as completed Oct 3, 2017

dtonys added a commit to dtonys/map-places that referenced this issue Dec 19, 2017

Fixed missing element issues by calling update on wrapper component

acffe63

- enzymejs/enzyme#1153 (comment)

ljharb reopened this Jan 12, 2018

ljharb added the package: react adapter: 16 label Jan 12, 2018

attekei mentioned this issue Jan 24, 2018

React 16 (Step 2): Enzyme Strikes Back metabase/metabase#6757

Closed

3 tasks

ericsoco mentioned this issue Jul 6, 2018

mount() wrapper is populated before componentDidMount() #1708

Closed

ashfurrow mentioned this issue Aug 20, 2018

Navigates to payment after shipment step artsy/reaction#1160

Merged

ljharb closed this as completed Sep 1, 2018

z2014 mentioned this issue Dec 18, 2018

年轻时，我不写单元测试 z2014/Blog#16

Open

marcelomorgado mentioned this issue Dec 18, 2018

Add a test to the test suite confirming that Account.create() works in React Native env tasitlabs/tasit-apps#12

Closed

This comment has been minimized.

Sign in to view

Sharakai mentioned this issue Apr 9, 2019

[Popper] Fix to defer setting of exited state to Transition component mui/material-ui#15250

Merged

1 task

PierreTurnbull mentioned this issue Dec 28, 2021

Fixed doc for "update" PierreTurnbull/enzyme#1

Open

enzyme@3: wrapper is not updated even if there was a new render #1153

enzyme@3: wrapper is not updated even if there was a new render #1153

Comments

deepsweet commented Sep 26, 2017 • edited Loading

ljharb commented Sep 26, 2017

deepsweet commented Sep 26, 2017

j4k commented Sep 26, 2017

yesmeck commented Sep 27, 2017 • edited Loading

yesmeck commented Sep 27, 2017

mx-scissortail commented Sep 27, 2017

iantanwx commented Sep 28, 2017

gziolo commented Sep 29, 2017

tleunen commented Sep 29, 2017

lelandrichardson commented Oct 3, 2017

mrbinky3000 commented Nov 27, 2017

ljharb commented Nov 28, 2017

mrbinky3000 commented Nov 28, 2017 • edited Loading

ljharb commented Nov 29, 2017

mrbinky3000 commented Nov 29, 2017

mrt123 commented Jan 11, 2018 • edited Loading

mkermani144 commented Jan 28, 2018 • edited Loading

Duskfall commented Apr 13, 2018

maloguertin commented Aug 7, 2018

ljharb commented Aug 7, 2018

ljharb commented Sep 1, 2018

lucasdeassis commented Sep 3, 2018

guofei0723 commented Dec 14, 2018 • edited Loading

ljharb commented Dec 14, 2018

This comment has been minimized.

This comment has been minimized.

pvanny1124 commented Jan 6, 2019 via email

pvanny1124 commented Jan 6, 2019 via email

ljharb commented Jan 6, 2019

Finesse commented Feb 10, 2019 • edited Loading

ljharb commented Feb 10, 2019

Jlevett commented Mar 11, 2019

Finesse commented Mar 11, 2019

RaiVaibhav commented Sep 19, 2019 • edited Loading

brendangibson commented Oct 1, 2019

guruusingh2033 commented Feb 27, 2020 • edited Loading

ljharb commented Feb 27, 2020

guruusingh2033 commented Feb 28, 2020 • edited by ljharb Loading

ljharb commented Feb 28, 2020

guruusingh2033 commented Feb 28, 2020

ljharb commented Feb 28, 2020

deepsweet commented Sep 26, 2017 •

edited

Loading

yesmeck commented Sep 27, 2017 •

edited

Loading

mrbinky3000 commented Nov 28, 2017 •

edited

Loading

mrt123 commented Jan 11, 2018 •

edited

Loading

mkermani144 commented Jan 28, 2018 •

edited

Loading

guofei0723 commented Dec 14, 2018 •

edited

Loading

Finesse commented Feb 10, 2019 •

edited

Loading

RaiVaibhav commented Sep 19, 2019 •

edited

Loading

guruusingh2033 commented Feb 27, 2020 •

edited

Loading

guruusingh2033 commented Feb 28, 2020 •

edited by ljharb

Loading