chore: fix JavaScript lint error (issue #9067)#9068
chore: fix JavaScript lint error (issue #9067)#9068Ankit-Trivedi-02 wants to merge 1 commit intostdlib-js:developfrom
Conversation
|
Hello! Thank you for your contribution to stdlib. We noticed that the contributing guidelines acknowledgment is missing from your pull request. Here's what you need to do:
This acknowledgment confirms that you've read the guidelines, which include:
We can't review or accept contributions without this acknowledgment. Thank you for your understanding and cooperation. We look forward to reviewing your contribution! |
Coverage Report
The above coverage report was generated for the changes in this PR. |
|
As the upstream issue was closed as "not planned" (ref: #9067), I'll go ahead and close this PR. Thank you again for your interest in stdlib. We look forward to your future contributions! |
Resolves #9067.
Description
This pull request fixes a JavaScript/TypeScript linting error caused by the use of an explicit
anytype in a TypeScript declaration file.Specifically, this change replaces
anywithunknownin the type definition forisSignedIntegerDataType, bringing the file into compliance with stdlib linting rules and TypeScript best practices.Related Issues
This pull request has the following related issues:
Questions
No.
Other
No.
Checklist
AI Assistance
If you answered "yes" above, how did you use AI assistance?
Disclosure
I consulted ChatGPT to understand the linting error and confirm the appropriate TypeScript type replacement. The code change itself was authored manually.
Checklist