David

@xuzhg and @habbes we should have support for .Net 6 alongside Net 5.0 to mirror the AspNetCore version. No tests break so far while testing.

ODataError.ToString() method outputs JSON that is not compliant with OData spec ### Reproduce steps The following code ` var error = new ODataError(){ Message = "Error" }; var json =...

@xuzhg one improvement that could be added is the possibility of parsing urls in a case insensitive manner. This allows canonicalized urls to be parsed without any errors.

Found that using `ParseDynamicPathSegmentFunc` could have one override this behavior easily.

@ThomasBarnekow @mukesh-shobhit Looking into the issue. @ImGonaRot Should the right semantics for deep insert be ``` Parent p = new Parent(); // set parent properties Child c = new Child();...

@fededim The issue is currently being worked on so it can be supported across our tooling.

@fededim I really can't give you a timeline for the whole delivery but you may see some of the pieces ship with some of our expected releases sometime through the...

@henrikdahl8240 Could you try to see if the issue exists on EF core `2.x`? We are aware of some limitations of using EF core 3.x and it is possible to...

@StefanoVuerich Thank you for reporting this, This would be a great feature to have and we would like to welcome any contributions if you are open to contribute.

@kccarter76 Thank you for your contribution, Kindly address the above comments.