fix: modify nested ternary operators and any type in useTexture

[Gaic4o]

Why

Since there is a nested ternary operator and an any type, we refactored the nested ternary operator to make it easier to understand and maintain, and modified the any type.

What

• Things that were of type any were changed to type unknown.
• We refactored the ternary operator type nested in the MappedTextureType type to make it easier to understand and maintain.
• Simplify texture processing logic in useEffect to handle various input types more uniformly.
• Because the string type is not a subtype of any[], it always returns string. So I removed the extends any[] type and modified the code to make it easier to understand.

Checklist

• Ready to be merged

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
drei	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Mar 17, 2024 7:43am

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

[drcmda]

thanks for all these fixes @Gaic4o really appreciate it! could you write us over at the discord to discuss administrative rights? i think fixes like these wouldn't have to site there for 2 weeks until somebody with time looks at it, it could go quicker. :)

[github-actions]

🎉 This PR is included in version 9.103.1 🎉

The release is available on:

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

Your semantic-release bot 📦🚀

[Gaic4o]

@drcmda
drei fix Thank you for your prompt response and the opportunity to further discuss the following issues.
Next time, I will contact you through Discord.
Thank you again for contacting us.