Suggested way to specifying default types for useNavigation, Link, ref etc. is against a recommended eslint rule

[janschloss]

Hello,

in this document it is suggested to declare a module for specifying default types for useNavigation, Link, ref etc.: https://github.com/react-navigation/react-navigation.github.io/blob/main/versioned_docs/version-6.x/typescript.md#specifying-default-types-for-usenavigation-link-ref-etc

However the eslint rule no-namespace which is part of the recommended rules for the TypeScript plugin disapproves of it: https://github.com/typescript-eslint/typescript-eslint/blob/v5.2.0/packages/eslint-plugin/docs/rules/no-namespace.md

[janschloss]

Is there any opinion on this?

[Adnan-Bacic]

while already on the topic of these types, it also gives an error for extending to an empty interface, referring to this rule:

https://github.com/typescript-eslint/typescript-eslint/blob/v5.2.0/packages/eslint-plugin/docs/rules/no-empty-interface.md

[ChromeQ]

I would also like to know of a way to achieve this without adding some ts-ignore

[satya164]

Linter warnings are about potential issues, and in this case purely code-style and not actual problems.