You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, when creating the LargeFileUpload object or the PageIterator object, we are passing a Client object which is used to make the requests.
The current design creates limitations in customizing the GraphRequest object options.
Example - To pass custom headers in the PageIterator, we pass a requestOptions parameter while creating the PageIterator object.
Another problem I came across was when working on #359. The response format of Outlook and OneDrive are different and I need to customize the ResponseType in the GraphRequest object.
The design of the task classes should be updated to allow easy customizations and changeability. The relations between the classes can be reengineered. Example - use a behavioral design pattern.
Currently, when creating the
LargeFileUpload
object or thePageIterator
object, we are passing aClient
object which is used to make the requests.The current design creates limitations in customizing the
GraphRequest
object options.Example - To pass custom headers in the
PageIterator
, we pass arequestOptions
parameter while creating thePageIterator
object.Another problem I came across was when working on #359. The response format of Outlook and OneDrive are different and I need to customize the
ResponseType
in theGraphRequest
object.Related to - microsoftgraph/msgraph-sdk-design#37
The design of the task classes should be updated to allow easy customizations and changeability. The relations between the classes can be reengineered. Example - use a behavioral design pattern.
AB#7642
The text was updated successfully, but these errors were encountered: