feat: add support for reachabilityMethod to specify GET or HEAD

[CaptainJeff]

Overview

Added in support for an optional field in NetInfoConfiguration for reachabilityMethod which accepts either HEAD or GET. Some API endpoints don't support HEAD requests and will return a 405 instead of a 204.

Test Plan

I set my default configuration to

{
  reachabilityUrl: 'https://clients3.google.com/generate_204',
  reachabilityMethod: 'GET',
  reachabilityTest: (response: Response): Promise<boolean> =>
    Promise.resolve(response.status === 204),
  reachabilityShortTimeout: 5 * 1000, // 5s
  reachabilityLongTimeout: 60 * 1000, // 60s
  reachabilityRequestTimeout: 15 * 1000, // 15s
  reachabilityShouldRun: (): boolean => true,
  shouldFetchWiFiSSID: false,
  useNativeReachability: true
};

And was able to verify the request was being made as a GET request instead of HEAD request

[mikehardy]

certainly seems reasonable, and backwards-compatible makes it easy to release, let's see what CI thinks then, sure :-). Thanks for posting this

[mikehardy]

formatting -

/home/runner/work/react-native-netinfo/react-native-netinfo/src/internal/types.ts
Warning:   10:13  warning  'NetInfoStateType' is already declared in the upper scope on line 10 column 13           no-shadow
Error:   22:47  error    Insert `;`                                                                               prettier/prettier
Warning:   24:13  warning  'NetInfoCellularGeneration' is already declared in the upper scope on line 24 column 13  no-shadow

I believe the targets are in package.json for local verification?

[mikehardy]

Now it doesn't just look functional but prettier should agree it is pretty as well...

[CaptainJeff]

hahahah thanks @mikehardy!!! Appreciate your help, as always

[matt-oakes]

🎉 This PR is included in version 9.2.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀