Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

updater-explicit-return-type No longer needed with NoInfer #4280

Open
1 of 2 tasks
david-shortman opened this issue Mar 24, 2024 · 2 comments
Open
1 of 2 tasks

updater-explicit-return-type No longer needed with NoInfer #4280

david-shortman opened this issue Mar 24, 2024 · 2 comments

Comments

@david-shortman
Copy link
Contributor

Which @ngrx/* package(s) are relevant/related to the feature request?

component-store

Information

I'm pretty sure with NoInfer in TS 5.4 that we can avoid the problem of needing explicit return types for updaters. This may be true other places in other packages, too.

Describe any alternatives/workarounds you're currently using

No response

I would be willing to submit a PR to fix this issue

  • Yes
  • No
@timdeschryver
Copy link
Member

This will be something to test if NoInfer does fix this issue.
If it does we can indeed remove the two (I think) rules.

@Harpush
Copy link

Harpush commented May 5, 2024

I played with no infer recently and I don't think it solves it...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants