Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Match children before and after interpolation #512

Merged
merged 2 commits into from
Mar 3, 2017

Conversation

eronisko
Copy link
Contributor

Proposed fix for #508.

@ljharb
Copy link
Member

ljharb commented Aug 4, 2016

I think this LGTM, pending another contrib's OK, and a rebase.

@ljharb
Copy link
Member

ljharb commented Aug 4, 2016

I'm not sure yet if this is a patch or a minor.

@sahat
Copy link

sahat commented Aug 11, 2016

Probably better to be on a safe side by making it a minor version instead of a patch.

@ljharb
Copy link
Member

ljharb commented Aug 11, 2016

That's not really safer, since neither is supposed to have a breaking change :-)

@sahat
Copy link

sahat commented Aug 11, 2016

Ah, that came out wrong. I was thinking of a versioning scenario that doesn't apply here and in the case where it does cause a breaking change accidentally by slipping through existing tests. Flip a coin or use your best judgement then. ;)

src/Utils.js Outdated

for (let i = 0; i < childrenArray.length; i++) {
const child = childrenArray[i];
const simplifiedChild = simplifiedArray.pop();
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

how about calling this previousChild?

@nfcampos
Copy link
Collaborator

nfcampos commented Aug 12, 2016

@ljharb if we define majors for enzyme as 'some tests that passed/failed with the previous version now will, respectively, fail/pass' then this is a major. if not it's a patch I think

@nfcampos
Copy link
Collaborator

nfcampos commented Aug 12, 2016

LGTM pending my minor comments being addressed

@ljharb
Copy link
Member

ljharb commented Aug 12, 2016

@nfcampos it's a minor if it's a new feature, but that suggests it's an intentional change which makes tests have different results, which makes it major. If tests were never supposed to have the current results and this fixes it, it's a patch. So, as you say - just very fuzzy :-/

@eronisko eronisko force-pushed the interpolated_children branch from 89695f9 to 106c89e Compare August 13, 2016 18:55
@nfcampos
Copy link
Collaborator

LGTM after the changes, now we just need to decide on what kind of change this is

@sahat
Copy link

sahat commented Sep 10, 2016

Has there been any consensus on whether to release this under minor, major or patch release?

@ljharb
Copy link
Member

ljharb commented Mar 2, 2017

@eronisko are you able to rebase this on top of latest master? it'd be great to get this in.

@eronisko eronisko force-pushed the interpolated_children branch from 298bd6c to 58820e0 Compare March 2, 2017 23:09
@eronisko
Copy link
Contributor Author

eronisko commented Mar 2, 2017

@ljharb done

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants