Michael Pizzo

A fix for this issue on the Azure AD Graph side was identified and merged. There was a freeze on deployments over the holiday week-end, but it should start to...

Bunch of questions about how this works for edge cases. Perhaps those edge cases never apply due to how the resource context is constructed, but I want to be sure...

Would love to see this fixed.

@corranrogue9 -- may be related to the count issues you have been looking into recently.

There are (at least) two issues -- 1) How to modify the SelectExpandClause in the query options. Seems like we should be able to clone/copy a new SelectExpandClause without the...

Since IEEE754Compatible defaults to false, the only time someone would care about it would be if they needed int64 returned as string (in which case, they would explicitly set it...

Note in ODataMediaTypesTest.cs, there are unit tests for each value which should be added for the new IEEE754Compatible media types. i.e.: [Fact] public void ApplicationJsonIEEE754CompatibleTrue_Value() { Assert.Equal("application/json;IEEE754Compatible=true", ODataMediaTypes.ApplicationJsonIEEE754CompatibleTrueToString()); } etc......

I think autoexpand will end up being key to this issue. Because it's autoexpand, we will try and generate the nav link for which we need key values. I suspect...

Silently ignoring a filter could be a critical security/data corruption issue.

IODataEdmTypeSerializer could solve the serialization/deserialization, but what other functionality do you want with the property? i.e., do you want to be able to filter/sort on it? How would it be...