fix: TypeScript ESLint unbound-method errors in Auth0 context interface #1368
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #1334
This PR resolves TypeScript ESLint
unbound-methoderrors that occurred when using strict type-checking configurations with the react-native-auth0 SDK. The issue was reported when users enabled therecommended-type-checkedpreset from@typescript-eslint, which flagged destructured methods from theuseAuth0()hook.Changes
src/hooks/Auth0Context.tsAuth0ContextInterfacefrom method syntax (methodName(): Type) to arrow function property syntax (methodName: () => Type)thiscontext and are safe to destructuresrc/platforms/native/bridge/NativeBridgeManager.ts.bind(Auth0NativeModule)when passing to thea0_callwrapperthiscontext preservation when calling native methodseslint.config.mjs@typescript-eslint/unbound-methodruletypescript-eslintpackage for unified configurationpackage.jsontypescript-eslintas a dev dependency for ESLint configurationTesting
unbound-methoderrors withrecommended-type-checkedconfigBreaking Changes
None. This is a backward-compatible change that only affects type definitions to improve compatibility with strict TypeScript ESLint configurations.
Developer Experience Impact
✅ Positive Impact: Developers using strict TypeScript ESLint configurations (like
recommended-type-checked) can now use the SDK without linting errors when destructuring methods from theuseAuth0()hook.