Mastering Fetch Requests: A Comprehensive Guide to Customization

Harmonize the properties of ExternalResource to fully match all the arguements of the fetch request

To fully customize a fetch request, you would need to consider the following parameters:

1. URL: This is the most important parameter. It is the address of the resource on the web you want to fetch.
2. Method: This is the HTTP method you want to use for your request. It could be GET, POST, PUT, DELETE, etc.
3. Headers: This is an object representing any HTTP headers you want to include in your request. It could include content type, authorization, etc.
4. Body: This is the data you want to send with your request. It is used with methods like POST or PUT.
5. Mode: This is the mode you want to use for the request. It could be cors, no-cors, same-origin, or navigate.
6. Credentials: This is the request credentials you want to use for the request. It could be include, same-origin, or omit.
7. Cache: This is the cache mode you want to use for the request. It could be default, no-store, reload, no-cache, force-cache, or only-if-cached.
8. Redirect: This is the redirect mode to use. It could be follow, error, or manual.
9. Referrer: This is the referrer of the request. It could be a URL or a string like no-referrer, client, or a URL.
10. ReferrerPolicy: This is the referrer policy to use for the request. It could be no-referrer, no-referrer-when-downgrade, origin, origin-when-cross-origin, unsafe-url, etc.
11. Integrity: This is the subresource integrity value of the request. It is a hash of the resource you're fetching that ensures the resource hasn't been tampered with.
12. Keepalive: This is a boolean that indicates whether or not the browser should keep the connection alive.

By manipulating these parameters, you can fully customize your fetch request to suit your specific needs.

Harmonize the properties of ExternalResource to fully match all the arguments of the fetch request, as well as the control parameters required to run the fetch logic.