fix: headers cannot be set

[nmsbnmsb1]

Problem: When using options.headers = { ...header }, the headers were not correctly applied to the request.

Solution: I replaced options.headers = { ...header } with options.headers = header. By assigning the headers directly, the issue is resolved, and the HTTP headers are now set correctly.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
shadcnui-boilerplate-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Sep 20, 2024 9:56am

[vercel]

@nmsbnmsb1 is attempting to deploy a commit to the TinsFox Studio Team on Vercel.

A member of the Team first needs to authorize it.

[TinsFox]

@nmsbnmsb1

Hey, can you explain where exactly it is not set properly?

It would be great if you could provide screenshots.

My test here is normal. This is my test result:

[nmsbnmsb1]

My code like this:
const header = new Headers(options.headers);
const token = getToken();
if (token) {
header.append("Token", token);
}
options.headers = header;

I believe this Header instance is used for setting headers, so I used its API to configure them.

When I used the destructuring operator，
options.headers ={ ... header }
I found that I couldn’t add the Token field to the HTTP headers, so I made this modification
options.headers = header

If this wasn’t your intention, please ignore my request.
Thanks : )

[TinsFox]

Can you try this code snippet?

const token = getToken();
if (token) {
	header.set("Token", token)
}

Maybe you should use set instead of append.

[nmsbnmsb1]

Hello. I have tried. Here are the results.

Please verify and test.
Thanks

[TinsFox]

@nmsbnmsb1 You are right, but I am working on other new features now. I will merge this PR later. Thanks