fix the example of Fetch_API with body and URLSearchParams

[NewUserHa]

Description

fix the example of Fetch_API with body and URLSearchParams and post

Motivation

fix error

Related issues and pull requests

Fixes #38115

[Josh-Cena]

@NewUserHa See my comment in the linked issue: this is intended, and none of the other code examples have method: "POST" explicitly. Do you want to update this PR to implement your other suggestion (showing sending the search params as URL instead of body) instead?

[NewUserHa]

I think if this code block is intended not able to run then it should be marked as a error block like the one below it,
and I hope the documentation can have an example for a practice example for "GET" having multiple query with the same key names because there is no good one after searched

[Josh-Cena]

Could you update other occurrences of the same issue as well?

[NewUserHa]

what about just updating the // ... to // ...incompleted code or // ...here need add more codes in this markdown page

[Josh-Cena]

I think adding method: "POST" doesn't hurt, and makes the example directly copiable, which is desirable.

[NewUserHa]

agree

[NewUserHa]

if in future updating the // ... to // ...incompleted code or // ...here need add more codes in this markdown page
can prevent reader from misunderstanding to that "// ..." means "my codes go there"

[Josh-Cena]

Per the discussion in the issue, we should:

• Introduce the method option first, then body, then headers; this way when we say "requests with body can only be sent with POST", it doesn't appear confusing or out of context
• When discussing any fetch call with a body we should explicitly use method

[github-actions]

Preview URLs

• /en-US/docs/Web/API/Fetch_API/Using_Fetch

Flaws (2)

URL: /en-US/docs/Web/API/Fetch_API/Using_Fetch
Title: Using the Fetch API
Flaw count: 2

• broken_links:
  • /en-US/docs/Glossary/stringifier is ill cased
• macros:
  • Macro produces link /en-US/docs/Glossary/stringifier which is a redirect