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

(Mongo) Function MongoUpdateProperty results in unwanted side-effect #576

Open
kharybdys opened this issue Jan 4, 2021 · 1 comment
Open

Comments

@kharybdys
Copy link
Contributor

If you're using MongoUpdateProperty to update a message that represents a Mongo document in the database (eg the MatchForm collection), it results in not just updating the property but also adding an __id property if it doesn't exist yet. This property should only exist within elements of an array so it's unwanted.

First analysis is that this is due to the way MongoUpdateProperty retrieves the message(s) to change. That makes the message type "array_element" and that ensures the MessageCodec adds the __id property.

@kharybdys
Copy link
Contributor Author

The __id property generated isn't causing any problems, it just looks odd. So urgency is low.

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