[Muthurathinam (muthurathinam)]

Fetch API options

There are node environment specific needs such as passing agent (http(s).Agent instance, allows custom proxy etc.), timeout for request, number of follows for a continuous redirect etc., and these options needs to be passed to fetch call through its RequestInit param (second param).

We have enabled two ways to pass these options for a request.

1. Passing options while initializing the GraphClient. Options can be any Node specific or Fetch standard
   Note: This configuration applies to all the requests that are made through GraphClient

const client = MicrosoftGraph.init({
    defaultVersion: 'v1.0',
    debugLogging: true,
    authProvider: (done) => {
        done(null, secrets.accessToken);
    },
    fetchOptions: {
        timeout: 5,
        follow: 20
    }
});

2. Pass in for every request with .option and .options functionality.
   Note: This applies to the particular request

client
    .api('/me')
    .select("displayName")
    .option("redirect", "allow")
    .options({
        timeout: "500"
    })
    .get((err, res) => {
        if (err) {
            console.log(err)
            return;
        }
        console.log(res.displayName);
    });

Bugs Fixed:

1. Unable to use the library through a proxy #97
2. Timeout property of superagent library should be exposed #39

[Michael Mainer (MIchaelMainer)]

Comment: I'd like for scenarios like this to be checked with either a pre-commit hook script or via CI.

[Muthurathinam (muthurathinam)]

sounds like a very good option. will do that.!

[Michael Mainer (MIchaelMainer)]

Not part of this PR but we should include search and format as values in oDataQueryNames

[Muthurathinam (muthurathinam)]

Yeah that is something we have in our plate. will make a different PR for that.

[Michael Mainer (MIchaelMainer)]

Make this a heading 3

[Deepak Agrawal (deepak2016)]

Looks good.