Skip to content

fix #18: nested props are ignored if the first one is undefined #19

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

Merged
merged 1 commit into from
May 23, 2022

Conversation

benbender
Copy link
Contributor

@benbender benbender commented May 18, 2022

I did a little research on #18 and it turns out that the bug is only present if the first prop is undefined. This pr fixes the issue and adds a test-case.

closes #18

@google-cla
Copy link

google-cla bot commented May 18, 2022

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

For more information, open the CLA check for this pull request.

@argyleink
Copy link
Contributor

sorry reviewing these great PRs took a few days, been afk

@argyleink argyleink merged commit 6e15ba8 into GoogleChromeLabs:main May 23, 2022
@benbender
Copy link
Contributor Author

benbender commented May 23, 2022

@argyleink No prob. Living outside of github is a thing I've heard of ;)

(Edit: Didn't saw the release. Need moar coffee...)

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.

Bug: Nested properties are purged if the first prop is not defined
2 participants