Bug: ESLint - Custom hook in a typescript class method trigger an error about class component about react

[markerikson]

@nbrignol Why are you trying to write a hook as a class? There's no reason to.

[yanup2913]

@nbrignol you are returning react hooks from the class based component that in itself breaking the reack hook rules. Let us know your usecase we will try to help you with that.

[nbrignol]

@nbrignol Why are you trying to write a hook as a class? There's no reason to.

Because I want to :p. Class methods are functions, right ?
And in this case because classes are great for abstractions : I can abstract my hook behind an interface for exemple.

Actually this is working very well. The problems comes from the linter's message that is not right.
If it's forbidden (I'd like to know why and) the message should be dedicated : this is not a class component.
And if it's not (what I think and hope) the message should not be triggered here.

[markerikson]

@nbrignol there is genuinely no good reason to do this that I can think of. There's no benefit. A hook doesn't need to be "abstracted behind an interface". It shouldn't have access to class field methods. It needs to be based solely on the inputs and calling other hooks.

You're running into a problem you've created for yourself :) Just write it as a normal standalone function and move on.

[nbrignol]

@nbrignol there is genuinely no good reason to do this that I can think of. There's no benefit. A hook doesn't need to be "abstracted behind an interface". It shouldn't have access to class field methods. It needs to be based solely on the inputs and calling other hooks.

You're running into a problem you've created for yourself :) Just write it as a normal standalone function and move on.

Again I think this is not the point.

Either it's a technical limitation and can't do that : I can understand, and I think you should add a dedicated message because this one does not match the context;
or it's not a problem in itself (even if is not a traditional way to work) and the error should not be triggered.

In both case, ESLint doesn't handle well this situation, that's why I am filling this "bug".
(Of course I understand this is not a priority matter for the project !)

Thanks for your time.