Skip to content

fix: calculate changes for input properties like component properties #380

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

Conversation

shaman-apprentice
Copy link

ref #365

}
}
setComponentInputs(fixture, newComponentInputs);
const changesInComponentInput = update(fixture, renderedInputKeys, newComponentInputs, setComponentInputs);
renderedInputKeys = Object.keys(newComponentInputs);

const newComponentOutputs = properties?.componentOutputs ?? {};
Copy link
Author

@shaman-apprentice shaman-apprentice Apr 2, 2023

Choose a reason for hiding this comment

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

[JFI] On a quick local test, changes in component outputs are not included in ngOnChanges. So I think we only need to calculate changes from component inputs and component properties.

Copy link
Member

Choose a reason for hiding this comment

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

Sounds good to me!
Thanks a lot for this, I was just going to take a stab at it but you beat me to it 👍

@timdeschryver timdeschryver merged commit 33d0069 into testing-library:remove-deprecations Apr 3, 2023
@shaman-apprentice shaman-apprentice deleted the fix/#365/changes-for-input-properties branch April 3, 2023 21:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants