-
Notifications
You must be signed in to change notification settings - Fork 28
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
Kiota Ignores Repeated Serialization #1561
Comments
Hi @buchananwill , While I appreciate the level of details that you provided, I'm not sure I understand why you created an additional issue here? Maybe I missed something but it seems to be the same request as the issue I originally had created? |
Thanks for clarifying. I think you're indeed right - I am more-or-less duplicating your post. Before writing, I read around a few of the related issues and some of them were more specific about serialization of collections, or the serializeAsStream() method. Having re-read the comments on your post, #1131, you have indeed covered the points I've made here. I guess I conflated/confused the different threads and wasn't satisfied that the behaviour was concisely documented in the way I understood it. My key takeaway: any repeated serialization results in empty lists, or entirely ignored properties. |
Thanks for confirming, closing as duplicate, feel free to add additional context to the original issue. |
I am integrating Kiota/Graph with my existing application API, and while running various test cases to understand the Kiota serializer, I discovered that some of the nested properties weren't serializing. I stripped the test case back to this minimum, and having looked at other open issues (in particular #1131 ), I understand that this behaviour is intentional?
However, it is was extremely unexpected. I would expect serialization to be a side-effect free operation, especially if carried out via a static helper method. Are there optimization reasons that make this non-repeatability necessary? Or could the design be changed to always serialize a full object? Alternatively, could a second method be provided (and more explanation in the documentation) that gives the choice of changed/all properties? My default expectation would be the full object, with changed-only as a option.
Output:
The text was updated successfully, but these errors were encountered: