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

ChangingContext.Merged creates duplicate is_null attributes on any incoming property when a type attribute exists #57

Open
kentonvk opened this issue Oct 25, 2023 · 0 comments

Comments

@kentonvk
Copy link

When using the ChangingContext.Merged property, given an initial Item that contains a property like:
<property_name type='Some Type' is_null='1'></property_name>, the resulting merged item result is invalid due to the property above having 2 is_null attributes.
I have confirmed that removing the type attribute from the incoming property works as expected.

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

No branches or pull requests

1 participant