You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Now the SDK has been converted to TypeScript, it should not use any anymore.
Use of any causes problems for library consumers that use TypeScript in strict mode, as well as errors from the recommended set of TypeScript ESLint rules like https://typescript-eslint.io/rules/no-explicit-any/.
any is an escape hatch that disables type checking and allows you to access arbitrary properties, even ones that don’t exist.
Describe the solution you'd like
Use unknown instead of any. This would be a breaking change so would require a major version bump following SemVer.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Now the SDK has been converted to TypeScript, it should not use
any
anymore.Use of
any
causes problems for library consumers that use TypeScript in strict mode, as well as errors from the recommended set of TypeScript ESLint rules like https://typescript-eslint.io/rules/no-explicit-any/.any
is an escape hatch that disables type checking and allows you to access arbitrary properties, even ones that don’t exist.Describe the solution you'd like
Use
unknown
instead ofany
. This would be a breaking change so would require a major version bump following SemVer.The text was updated successfully, but these errors were encountered: