[no-call-expression] Add support for excluding specific attribute names about angular-eslint

[JamesHenry]

In my example I am wrapping a Promise?

 protected slowAction$ = defer(() => from(YOUR_PROMISE_HERE));

[json-derulo]

Why are you using a function which returns the Observable, instead of working with the Observable directly? With your pattern, for each change detection cycle, a new Observable will be created. Sounds like an antipattern to me.

[maxfriedmann]

I changed the example above and added parts of the directive's implementation. Its a function returning a function that returns an Observable/Promise. The function only gets called when clicking on the host element (<my-custom-component/>). That's the reason why I chose this weird construct.

[JamesHenry]

@maxfriedmann it might be helpful if you could share a minimal end to end example in a stackblitz?

[maxfriedmann]

@JamesHenry sure: https://stackblitz.com/edit/angular-kxrwgv

[JamesHenry]

@maxfriedmann I think using an Observable using rxjs's defer would be preferable here:

https://stackblitz.com/edit/angular-rju8dt?file=src%2Fmain.ts

[maxfriedmann]

Thank you for taking the time. You're right, unfortunately this would require a massive migration in our source (around ~2300 places where [loadingFn] is currently used).

And, more important, that would not work with promises.

[maxfriedmann]

Okay, I'll give this a try. Thank you for your time!

[JamesHenry]

Cool hope that's useful! For changes that don't make sense for everyone that uses angular-eslint, it's always possible to build your own lint rules using @angular-eslint/utils so that it also something you can explore if you want to enforce particular unique usage