Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Feature Request] - for the httpclient keep toPromise method after rxjs 7 (removed in rxjs 8)

See original GitHub issue

🚀 feature request

Relevant Package

This feature request is for @angular/common/http

Description

https://indepth.dev/rxjs-heads-up-topromise-is-being-deprecated/

Describe the solution you’d like

It looks like rxjs topromise is being deprecated. Could we have this method keep in the http client? It will again breaking and useless refactor, while has a valid method for the http client.

Describe alternatives you’ve considered

We would not like to refactor our codebase because rxjs will be breaking again and it is not adding an additional method after rxjs topromise is removed in rxjs v8.

Issue Analytics

State:
Created 3 years ago
Reactions:8
Comments:10 (7 by maintainers)

Top GitHub Comments

4reactions

Airbladercommented, Jun 13, 2020

By the way, a migration from toPromise to lastValueFrom can very likely be done automatically through a code migration. IMO that should be more than sufficient.

0reactions

angular-automatic-lock-bot[bot]commented, Jul 31, 2021

This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}