Skip to content

Enabling the requesting object to be logged out either via debug or in error object #457

Open
@anvilation

Description

@anvilation

Feature Request

Is your feature request related to a problem? Please describe

Whilst troubleshooting using the Large File request I kept getting a message indicating that the message was malformed. However, because I running my app in Node (console-based app) there was no way for me to meaningfully take the request object being generated by LargeFileUploadTask.createUploadSession

I eventually worked around it by going to the compiled library and putting some console.logs on the GraphRequest.send method.

Describe the solution you'd like

Not sure, I would imagine one of two options.

  1. when debug is turned on it also turns on the request object as well as the URL that you are requesting
  2. Add the request object to the error response.

Describe alternatives you've considered

So far the alternative is to hack at the compiled code which is not ideal.

Additional context

....

AB#9542

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions