Philip Gichuhi

Resolved in latest v1 release

We are yet to provide batch request support via the fluent API in 2.0-RC5. However, in the meantime you can create a Graph-configured guzzle client and configure batch requests on...

Authentication code snippet in README is fixed for v1 removing the `resource` parameter from the body. v2 preview abstracts away this issue using the Authentication Provider.

@minhvn adding multiple members within one request as shown in the [docs](https://learn.microsoft.com/en-us/graph/api/group-post-members?view=graph-rest-1.0&tabs=http#example-2-add-multiple-members-to-a-group-in-a-single-request) is NOT currently supported. Work to support `@odata.bind` is being tracked under #137. Kindly clarify the second part...

Moving forward, 2.0 will not be using `jsonSerialize()` and thanks, added the parameter/return type declarations changes to the Upgrade guide

As of [2.0.0-RC9](https://github.com/microsoftgraph/msgraph-sdk-php/releases/tag/2.0.0-RC9), PATCH requests return the deserialized response body

Idea to make the `Date` type useful in v1 as well & fix the Date serialization issue (https://github.com/microsoftgraph/msgraph-sdk-php/issues/704).. Would it be worthwhile to make the setters for Date types continue...

> > Idea to make the `Date` type useful in v1 as well & fix the Date serialization issue ([microsoftgraph/msgraph-sdk-php#704](https://github.com/microsoftgraph/msgraph-sdk-php/issues/704)).. > > Would it be worthwhile to make the setters...

PUT request with discrepancy (Uploading to OneDrive) has been logged https://github.com/microsoft/OpenAPI.NET.OData/issues/310

(Sorry to pick up this conversation after a long time) The callback approach and anonymous object/dictionary approach would require a developer to first figure out what query parameter options are...